Craig, If I'm not mistaken this has been discussed before on the list and there is a jira issue for it. I mean how to support start levels in pax construct. Unfortunately, Stuart does not have the time for it now (me neither), so teh only way to get that in is to do it yourself or wait till there is time for it.
http://issues.ops4j.org/browse/PAXCONSTRUCT-127 On Tue, Nov 3, 2009 at 5:22 PM, Ching, Craig <craig_ch...@bmc.com> wrote: > > The only part I don't like about this is that I had intended to use > > pax-import-bundle to maintain the bundles that need to be provisioned. > > Since I now have to have the .cm bundle provisioning spec in my > > runner.args and I like uniformity, I'm going to maintain all bundle > > provisioning specs in my runner.args instead. Ugly, but it'll work. > > > > Any further comments? > > > > Another downside to managing the provisioning in runner.args is that you > can't use maven properties to control bundle versions. That's going to be a > mess, especially with equinox's versioning ;-P > > Cheers, > Craig > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Alin Dreghiciu Software Developer My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.blogspot.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development.
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
