Re: [virgo-dev] Milestone 5

[Glyn Normington <gnormington@xxxxxxxxxx>]

The fix is to revert an earlier commit. The reverting commit is in the kernel: 11b0c2901154c9904eb9278aab2e3f842ab41a7c

Regards,
Glyn
On 7 Oct 2010, at 07:26, Iliev, Hristo wrote:

Hi Glyn,

Can you provide details on the fix? It will happen on Virgo side from what I see in your mail, but I'm more interested if it will include a refactoring of the file structure?

Regards,
Hristo Iliev

-----Original Message-----
From: virgo-dev-bounces@xxxxxxxxxxx<mailto:virgo-dev-bounces@xxxxxxxxxxx> [mailto:virgo-dev-bounces@xxxxxxxxxxx] On Behalf Of Glyn Normington
Sent: Thursday, October 07, 2010 5:59 AM
To: Virgo Project
Subject: Re: [virgo-dev] Milestone 5

Hi Tim

Thanks for reporting the problem which was over-zealous reorganisation of the kernel directory layout on my part with insufficient regard to the tooling. Apologies for the inconvenience.

I've logged bug 32719 [1]  which will be fixed in Virgo 2.1.0.M06-incubation.

See the bug report for how to reconfigure the tooling as a temporary workaround. Here are the instructions for ease of reference:

1. Open the "Servers" window in the tooling.
2. Determine the Virgo server to be reconfigured.
3. Double click the Virgo server to open up the server window.
4. Navigate to the "Overview" pane.
5. Click the "Open launch configuration" link.
6. Navigate to the "Classpath" pane.
7. Select "User Entries".
8. Add each of the 5 JARs in the launcher directory to the classpath in turn (the order does not matter), by clicking "Add External JARs...", navigating to $SERVER_HOME/lib/launcher, and adding the JARs as necessary.
9. Back on the "Classpath" pane, once all 5 JARs have been added, click "Apply" then "Ok".

It should now be possible to launch Virgo as usual.

Regards,
Glyn

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=327169
On 5 Oct 2010, at 16:01, Tim Goeke wrote:

That's great news!  Thanks to everyone on the Virgo team, I'm looking forward to trying it out.

From the command line (on Mac) everything seems to be fine, but under STS 2.5 M3 updated to the latest snapshot, I am getting the following error:

Exception in thread "main" java.lang.NoClassDefFoundError: org/eclipse/virgo/osgi/launcher/Launcher
Caused by: java.lang.ClassNotFoundException: org.eclipse.virgo.osgi.launcher.Launcher
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:248)


I have not done much testing nor have I tried under STS on Windows.  I can confirm that M4 still starts normally under the snapshot STS.  Hopefully this is an easy fix!

Thanks,
Tim Goeke

On Tue, Oct 5, 2010 at 3:51 AM, Glyn Normington <gnormington@xxxxxxxxxx<mailto:gnormington@xxxxxxxxxx>> wrote:
Virgo 2.1.0.M05-incubation is available from the download page. See the release notes for details.

We are planning to release 2.1.0 by the end of October following a graduation/release review starting on 20 October.

Rgards,
Glyn
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx<mailto:virgo-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/virgo-dev

<ATT00001..txt>

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev