On 04/03/2014 03:27 PM, Sergey Bylokhov wrote:
On 03.04.2014 11:01, Yuri Nesterenko wrote:
On 04/02/2014 07:07 PM, Sergey Bylokhov wrote:
There's some sort of a logistics issue here. The existing corpus of
the client tests is huge, and making a drastic change like introducing
realSync would inevitably break some of them. Nobody knows
how many.
The operational plan is to give an important change some time
in limbo before adding it
to JDK/src -- but at the same time to do our porting job.
That would require some (a lot of) test run analysis with
internal JDK builds -- but in background.
I think it will be simple to add a few methods to the robot class. No?
Otherwise you have to change tests again? We can start from the simple
glade and type.
It will be integrated early and bugs will be found early as well. But
thats up to you.
Well yes, that part would be simple. But to move methods to the parent
also will be simple, and we will do it for some methods anyway.
For tests it is completely transparent from where some method come,
so they will not change.
Thanks,
-yan
