Magnusson, Geir wrote: > Its an element of uncertainty because if you change the load order, surprises > can happen.
I'm confused? The stubs do not participate in the bootclasspath order, which is defined by the properties file. > I understand the need for compilation, but don't see why they are necessary > in jars for deployment... Right, they are not needed at runtime because the VM provides its own version. They appear there to satisfy the compile-time requirements (and development-time visibility rules). FYI Our simple javac tool queries the VM it is running on to find out the location of the kernel and other bootclasspath jars. Regards, Tim > -----Original Message----- > From: Tim Ellison [mailto:[EMAIL PROTECTED] > Sent: Monday, June 26, 2006 02:30 AM Pacific Standard Time > To: harmony-dev@incubator.apache.org > Subject: Re: svn commit: r416738 - > /incubator/harmony/enhanced/drlvm/trunk/vm/vmcore/src/init/bootclasspath.properties > > Magnusson, Geir wrote: >> Isn't it better to not have the stubs around at all? Gets rid of one >> element of uncertainty - load order. > > As Mark points out, they are not referenced by the > bootclasspath.properties, which defines the load-order. However, they > are needed to allow Java code to compile (both our build scripts and our > Javac). > > Regards, > Tim > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
