2008/9/10 Chris Gummer <[EMAIL PROTECTED]> > Hi, > > I'm using the maven pax plugin for my OSGi development. Currently I'm using > the plugin to build my config.ini file and aggregate all my bundles for the > equinox framework. This is working perfectly at the moment. > > I'd like to package the equinox framework, that the plugin produces, as a > deployable artifact via maven. However, when using pax:provision the target > framework is always started. > > What I'd like to know is, is it possible to leverage pax:provision to > aggregate all my bundles, build the config.ini file, and NOT start the > framework so my build can continue? >
pax-provision has a "-Ddeploy=false" option, but this stops the provisioning just after creating the deployment pom that lists all the bundles, and before calling pax-runner. however, the config.ini file is built by pax-runner so what you're after is an option that will stop pax-runner just before it forks the framework process - unfortunately there is no such option at the moment, but it would be straightforward to add one. could you raise this as a pax-runner feature request on JIRA? http://issues.ops4j.org/jira/browse/PAXRUNNER and either Alin or I will fix it (you're also welcome to fix it yourself - the primary affected file is in the pax-runner-platform module called "PlatformImpl.java", but you'll also need to touch a few other files to add the new option...) [ this is also related to http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-91 ] Thanks, > Chris. > > ------------------------------ > Enter today! Win a Hotmail Go-Kart to race at > Bathurst.<http://www.livelife.ninemsn.com.au/compIntro.aspx?compId=4602> > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > -- Cheers, Stuart
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
