Description Borislav Kapukaranov 2010-09-10 12:30:51 EDT

Build Identifier: 2.1.0.M04-incubation

Currently Virgo has a very different file structure than the one used in Eclipse products and used by the P2 provisioning system. Since P2 requires specific Eclipse-like structure, adopting it to Virgo will enable it to be more easily provisioned with P2 in future when there will be some P2 Virgo repositories.

I've provided two patches that provide Eclipse-like file structure to Virgo.
One contains changes in the kernel project, in its packaging configurations, also config.ini file is included. 
The other patch changes the launcher in order to provide support for reading standard osgi properties such as these in the config.ini file (osgi.bundles instead of launcher.bundles) and to becoma aware of the slightly different syntax of the osgi.bundles property (startlevels etc.)

I didn't reported them separately since they are logically bound.

Also i've tested if Virgo with the new file structure applied is still compatible with STS(Springsource Tool Suite), and it is with little configuration required, that would most likely be avoided if the Virgo server adaptor adopts the new structure.
In order to run Virgo in STS now one needs to
1.change the path to the launcher properties to the path to the config.ini file
2.change the path to the java profile from 'lib' to 'plugins' 
3.change the path to the configuration area from osgi to configuration folder as is in the standard Equinox distribution (where the config.ini is located)
4. use the proper working directory

In order for all this to work the launcher patch must be applied first so that the kernel can download the updated version when it packages the Virgo zip file.

What do you think about that? 

Best Regards
Borislav

Reproducible: Always