Community
Participate
Working Groups
I need a "headless" facility (other than an ant task) that can be used to generate and update CompositeP2 repositories. Our build runs directly from Ant so using a Java task to invoke a custom ant runner to use the already available custom ant task is unwieldy. Below is the email thread sent to the p2-dev list that originated this request: ------------------------------ Andrew, Thanks. I'll file a bug. Having an ant script call a task that uses java to invoke a custom class to run ant, so I can use a specialized custom ant task doesn't seem very efficient. I could also write a script that cobbles together the composite xml files, but having a App that truly generates those files would be preferable. -Eric Andrew Niefer wrote: > > There is an ant task for this <p2.composite.repository> (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm). > Ant scripts can be run headless using the org.eclipse.ant.core.antRunner application. > > It doesn't look like there is a command line application to do this. There is a class that could be modified to do this probably without too much trouble. Can you raise a bug if you think we should do this. > > -Andrew > > >Eric Gwin wrote: >> >> I'm wondering is if there is any "headless" Java command-line facility >> for generation and updating of composite repositories. >> >> Any information would be appreciated. >> -- >> -Eric
We are getting short on time and limited on what we can do. The easiest way to implement this would be to create an application that simply end up exercising the CompositeRepositoryTasks (in org.eclipse.equinox.p2.repository.tools). Eric, would you have some cycles for this?
The CompositeRepositoryTask class is only in the ant class loader and can not be referenced from regular bundle code. Instead, CompositeRepositoryApplication is where to start. Make it implement IApplication, add some command line parsing and expose it in the plugin.xml.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
