Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox/p2/Getting Started"
(→Using the console) |
|||
| Line 21: | Line 21: | ||
[[Category:Provisioning]] | [[Category:Provisioning]] | ||
| − | [[Category:Equinox]] | + | [[Category:Equinox|Provisioning]] |
Revision as of 23:11, 25 June 2007
Getting the code
- Create a CVS repository connection to ":pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse". Hint: Select the quoted text, open the CVS Repositories view, and select "Paste Connection" or hit Ctrl+V to add the connection
- Expand HEAD -> equinox-incubator > provisioning
- Checkout org.eclipse.equinox.prov.releng
- File > Import > Team Project Set. Select "projectSet.psf" in the releng project checked out above
- Follow the instructions in com.thoughtworks.xstream/README.txt to load the xstream code (this is temporary until we sort out a story for XML serialization)
Running the tests
First, you need to populate an artifact and metadata server with some installable units to install. Do this by running the "Metadata Generator SDK" launch configuration in the "OSGi Framework" launch category. You may need to alter some of the properties on the "Arguments" tab in the launch configuration dialog before you run. At the least you will probably need to modify the argument "-Declipse.prov.metadataGenerator.eclipseBase=" to point to a valid Eclipse SDK install. 3.3 M6 is a good build to use as the eclipse base.
Next, run the provisioning by executing the "Test Director SDK" launch configuration. Again, you may need to tweak some of the launch configuration arguments based on your local drive structure.
Using the console
To use the provisioning console, you can run the "Provisioning Console" launch configuration. Type "help" on the console to get a list of available commands.