Mark, Well, I see your point. This strategy sounds reasonable, thank you very much for your efforts on integration.
Confusion is really not a problem, as it's the easiest problem to resolve. :) Vasily -----Original Message----- From: Mark Hindess [mailto:[EMAIL PROTECTED] Sent: Monday, May 22, 2006 10:25 PM To: harmony-dev@incubator.apache.org Subject: Re: [jira] Commented: (HARMONY-337) Contribution of RMI framework On 22 May 2006 at 21:20, "Zakharov, Vasily M" <[EMAIL PROTECTED]> wrote: > > By the way, if "rmi2" module is ITC donation and "rmi3" module is Intel > donation, then what is the contents of "rmi" module? See HARMONY-471. This JIRA was the first part of my trying to replace the rmi stubs with the contents of modules/rmi2. It is incomplete because the tests still need to be moved - and updated. modules/rmi2 should probably go away once the migration of tests is completed. Incidentally, don't read too much in to the names rmi, rmi2, rmi3. The main reason I didn't do the changes in place in the rmi2 tree was because of the difficulty of creating a patches/recipes for the moves and creation of new files. Specifically, you can't easily do "svn move blah blah.old" and then add a new blah with "svn add blah" without doing a commit in between. > And how the process of getting the actual RMI implementation for Harmony > is going to go? The above JIRA also introduce an ant variable, hy.rmi.module, that allows an rmi implementation to be selected at build time - using "ant -Dhy.rmi.module=rmi3". I hope that this will allow several implementations to co-exist and be easily evaluated. It may be that in order to take the best from both contributions a third implementation will be developed. The mechanism I put in place should allow for this. Unless someone beats me too it, I will try to construct a JIRA that integrates the modules/rmi3 tree. (I might try to do this one without moving to yet another new directory tree and confusing people even more.) Regards, Mark. > -----Original Message----- > From: Vasily Zakharov (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Monday, May 22, 2006 9:02 PM > To: Zakharov, Vasily M > Subject: [jira] Commented: (HARMONY-337) Contribution of RMI framework > > [ > http://issues.apache.org/jira/browse/HARMONY-337?page=3Dcomments#action_ 1= > 2 > 412803 ]=20 > > Vasily Zakharov commented on HARMONY-337: > ----------------------------------------- > > George, > > Thank you very much for the bringover, looks like rmi3 module is ok. > > Vasily > > > > Contribution of RMI framework > > ----------------------------- > > > > Key: HARMONY-337 > > URL: http://issues.apache.org/jira/browse/HARMONY-337 > > Project: Harmony > > Type: New Feature > > > Components: Contributions > > Reporter: Vasily Zakharov > > Assignee: George Harley > > Attachments: rmi_src_20060410_2125-Harmony.zip > > > > Contains independent implementation of Remote Method Invocation (RMI) > framework and some unit tests. > > The RMI framework enables an object in one virtual machine to call > methods of an object in another one, to create applications distributed > on various Java virtual machines on the same or different hosts. > > For more information see the documentation included. > > --=20 > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]