They are not just stubs, I remember I've fixed a bug there [1].
They are not VM-independent, DRLVM's kernel classes differ [2] Thanks, Mikhail [1] http://issues.apache.org/jira/browse/HARMONY-121 [2] http://svn.apache.org/viewvc/incubator/harmony/enhanced/drlvm/trunk/vm/vmcore/src/kernel_classes/javasrc/java/lang/System.java?revision=411782&view=markup 2006/6/6, Mark Hindess <[EMAIL PROTECTED]>:
On 6 June 2006 at 9:40, "Mikhail Loenko" <[EMAIL PROTECTED]> wrote: > 6) move kernel classes out of classlib > > possibly create /j9 directory in a root, where j9 binaries and kernel > classes will live Aren't these just compile against stubs? They aren't really j9 specific. If we remove them, we'd need to compile against a specific vm? Personally I'd prefer to keep the stubs and loose coupling. Regards, Mark. > 2006/6/6, Geir Magnusson Jr <[EMAIL PROTECTED]>: > > I'd like to discuss how we start to bring together the pieces of Harmony > > given our goal is Java SE with all the fixin's. > > > > We now have > > > > /classlib > > /jchevm > > /drlvm > > > > DRLVM and classlib work together (as I think we all like to see jchevm > > do too...) > > > > But given that we are a Java SE project (and not a VM project or a > > classlibrary project) I think it behooves us to start thinking how to > > organize at a higher level. We've been very focused on the classlib > > area, but that's only one part. > > > > So, I'd like to propose something like > > > > 1) a /deploy directory in root, as a peer to /classlib and /drlvm > > > > /classlib > > /deploy > > /drlvm > > > > 2) Maybe move the launcher out from classlib to > > > > /launcher > > > > 3) Maybe create > > > > /tools > > > > where the tool work can happen? > > > > 4) Have /drlvm and /classlib build-deploy into /deploy, rather than the > > local one > > > > 3) create a top level script such that > > > > build drlvm-jdk > > or > > build jchevm-jdk > > > > does what you expect, namely build the classlib artifacts and put in > > /deploy, build the VM of choice and drop in /deploy, builds the > > toolset,etc and go from there. We can create our HDK snapshots from it, > > and drop HDKs into it for use : > > > > /deploy > > /hdk/ > > /hdk1/ > > /hdk2/ > > /jdk > > /jre > > > > etc > > > > Comments? > > > > geir > > > > > > > > > > --------------------------------------------------------------------- > > 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]
--------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
