On 9/12/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote:
Hi Richard,
If this tweaking doesn't affect visible TestNG user interface then I
see nothing bad about converting the sample module. Especially in case
if we have volunteers who cannot stand without it any longer :)
I only redirect the concurrency support from java.util.concurrent to
backport-util-concurrent which is used by TestNG for java14. It should
not influence the UI. I will try the Eclipse plugin. ;-)
Another question is, where should we keep this tweaked version? Is
there any place from which it can be downloaded during the build or we
should keep tweaked jar in svn or ...
Temporarily, we will keep it in Harmony SVN.
BTW, I'm still volunteering to convert beans.
Great & Thanks a lot.
Regards,
2006/9/12, Richard Liang <[EMAIL PROTECTED]>:
> Hello,
>
> I have been discussing with the author of TestNG (Cedric) about
> Harmony using a tweaked TestNG which does not require
> java.util.concurrent. The feedback is we could use the tweaked TestNG
> as long as we do not re-distributed it. So now it's possible to deploy
> TestNG in Harmony.
>
> What do you think we take a simple module (prefs?) to run a pilot? Or
> let's waiting for the completion of j.u.concurrent. Thanks a lot.
>
> Best regards,
>
> --
> Richard Liang
> China Development Lab, IBM
--
Alexei Zakharov,
Intel Middleware Product Division
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Richard Liang
China Development Lab, IBM
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
