[corona-dev] Buckminster headless for Corona server use

[Thomas Hallgren <thomas@xxxxxxx>]

Hi,
As agreed on the dev conference call. Here's some info to get 
Buckminster headless running. Needless to say, we are very eager to help 
and answer questions.

The easiest way to get everything into your workspace is to use 
Buckminster. Simply install it from 
http://download.eclipse.org/technology/buckminster/updates. Once 
installed, you should be able to open a CQUERY and resolve it. Use 
Buckminster (the top menu) -> "Open a Component Query" and enter the URL 
http://www.eclipse.org/buckminster/samples/queries/buckminster.cquery. 
The Query editor opens and at the bottom you'll find the button 'Resolve 
and Materialize'. Click it and then watch the resolution/materialization 
take place. Once finished, and you're all set.

You can of course also check out everything manuall. All our stuff is 
reachable in CVS under 
:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/technology/org.eclipse.buckminster

Basic requirements for headless execution:
* A subset of headless bundles from Eclipse 3.2.x (details below)
* Java version is 1.5.
* The Buckminster plugins as detailed below.

The very core of buckminster consist of:

org.eclipse.buckminster.runtime
org.eclipse.buckminster.cmdline
org.eclipse.buckminster.installer
org.eclipse.buckminster.sax
org.eclipse.buckminster.core

The core is capable of resolving using URL's and to materialize a 
workspace from a BOM but not much more then that. We need a couple of 
repository specific plugins to make it really useful:

org.eclipse.buckminster.maven
org.eclipse.buckminster.cvs

With them, Buckminster will be able to resolve projects that have 
Buckminster meta-data (a CSPEC) or a Maven POM file. In order to 
understand the meta-data of OSGi bundles and and Eclipse features, we 
also need:

org.eclipse.buckminster.pde
org.eclipse.buckminster.jdt
org.eclipse.buckminster.ant

Now we have a fully configured Buckminster headless (well, I left out 
the P4 since nobody seems to use that nowadays). This configuration will 
of course introduce some dependencies on the Eclipse platform. Here is a 
complete list:

org.apache.ant
com.ibm.icu
org.eclipse.ant.core
org.eclipse.core.commands
org.eclipse.core.contenttype
org.eclipse.core.expressions
org.eclipse.core.filebuffers
org.eclipse.core.filesystem
org.eclipse.core.jobs
org.eclipse.core.resources
org.eclipse.core.runtime
org.eclipse.core.runtime.compatibility
org.eclipse.core.runtime.compatibility.auth
org.eclipse.core.runtime.compatibility.registry
org.eclipse.core.variables
org.eclipse.debug.core
org.eclipse.equinox.common
org.eclipse.equinox.preferences
org.eclipse.equinox.registry
org.eclipse.jdt.core
org.eclipse.jdt.debug
org.eclipse.jdt.launching
org.eclipse.osgi
org.eclipse.osgi.services
org.eclipse.pde.build
org.eclipse.pde.core
org.eclipse.team.core
org.eclipse.team.cvs.core
org.eclipse.text
org.eclipse.update.configurator
org.eclipse.update.core
org.junit4 (for now, this will be refactored out very soon)

Finally, you might want to add support for Subversion as well. In order 
to do that, you need:

org.eclipse.buckminster.svn
org.tigris.subversion.subclipse.core (downloaded from tigris.org)

Note, the easisest way to get everything into your workspace is of 
course to use Buckminster. Simply install it from 
http://download.eclipse.org/technology/buckminster/updates. Once 
installed, you should be able to do Buckminster (the top menu) -> "Open 
a Component Query" and enter the URL 
http://www.eclipse.org/buckminster/samples/queries/buckminster.cquery. 
The Query editor opens and at the bottom you'll find the button 
'Resolver and Materialize'. Click it and see the 
resolution/materialization take place. Once finished, and you're all set.




Kind Regards,
Thomas Hallgren