Community
Participate
Working Groups
Build Identifier: 2.1.0.M03-incubation Currently Virgo's classpath contains all items in /lib folder. Most of them are unnecessary and unused. I removed them and left only 4: org.eclipse.osgi org.eclipse.virgo.osgi.extensions.equinox org.eclipse.virgo.osgi.launcher org.eclipse.virgo.kernel.authentication With classpath that contains only these 4 items all virgo tests pass and virgo operates normally. I'm not quite sure if the org.eclipse.virgo.kernel.authenticationitem is needed - the tests pass without it, but since it is included in virgo's bootdelegation i figured it is used somehow so i included it in the cleaned up classpath just in case. Reproducible: Always
Created attachment 177966 [details] GIT patch for the cleaned up classpath - fixed in both .bat and .sh classpath scripts
Thanks for this contribution. I am actually implementing a more robust solution which does not require a list to be coded in the classpath scripts. Essentially I am reducing the set of JARs which were in lib to be just those needed on the classpath and then I'm moving those JARs into a lib/launcher directory. The classpath can then be all the JARs in lib/launcher. This will also have the nice side-effect of reducing the disk footprint of the installation since quite a few JARs were unnecessarily duplicated in lib. Note: shutdown JAR is needed in addition to those in your experiment so that the shutdown scripts work correctly.
Change committed and rippled. This will appear in milestone 5. If you want to take this for a spin before then, please build the kernel or the web server.
This has survived usage since then (and full ci-builds) and can be closed.
RC1 is planned instead of milestone 5.