Ahh,
that was good information Andreas, thanks!

/peter

GTalk:      neubauer.peter
Skype       peter.neubauer
Phone       +46 704 106975
LinkedIn   http://www.linkedin.com/in/neubauer
Twitter      http://twitter.com/peterneubauer

http://www.neo4j.org                - Relations count.
http://www.oredev.se                - The best thing since the wall came down.
http://www.linkedprocess.org   - Distributed computing on LinkedData scale



On Fri, Sep 18, 2009 at 6:16 PM, Andreas Kollegger
<akolleg...@tembopublic.org> wrote:
> It isn't obvious, I agree. After some digging and experimenting, I
> discovered that you can simply include start-levels by explicitly
> specifying the bundle provisioning in the plugin setup. By default,
> all project bundles will be provisioned, so this seems redundant,
> but this give you the opportunity to specify start level by appending
> to the bundle reference.
>
> For instance, I've got a project pom that provisions in this way:
>
>          <plugin>
>              <groupId>org.ops4j</groupId>
>              <artifactId>maven-pax-plugin</artifactId>
>              <version>1.4</version>
>              <configuration>
>                  <framework>felix</framework>
>                  <profiles>log,web</profiles>
>                  <!-- noDependencies=true to force all deployabled bundles
> to be part of a feature -->
>                  <noDependencies>true</noDependencies>
>                  <provision>
>
>  <param>scan-features:mvn:org.gatherdata.gather-commons/org.gatherdata.commons.features/${gather-commons.version}/xml/features!/gather-core,${dao.gather-dependenci...@2</param>
>
>  <param>smvn:org.gatherdata.gather-alert/org.gatherdata.alert.dao.neo4j/${gather-alert.versi...@2</param>
>                  </provision>
>              </configuration>
>          </plugin>
>
> Ignore the scan-features provision command, which uses karaf features for
> specifying
> a group of bundles. The second provision command with the "@2" at the end
> instructs
> pax-runner to provision that bundle at start level 2.
>
> Cheers,
> Andreas
>
>
> On Sep 18, 2009, at 11:32 AM, Andrew Woods wrote:
>
>> Hello All,
>> I have what seems like a simple problem (to which I hope to find a
>> simple solution). In using the maven-pax-plugin, I would like to be
>> able to start a specific bundle
>> (org.springframework.osgi.web.extender_1.2.0) at a start level higher
>> than the default of 5.
>> Clearly this is supported, but I have been unable to find the
>> documentation (either on the mailing list archives, pax-runner docs,
>> google...) describing the correct configuration.
>>
>> PAX-EXAM supports this with 'dependency_options' setting:
>> http://wiki.ops4j.org/display/paxexam/Configuration+using+Maven+Plugin
>>
>> And it would seem reasonable to pass a param into pax-runner within
>> the <provision> element of:
>>
>> http://www.ops4j.org/projects/pax/construct/maven-pax-plugin/provision-mojo.html
>>
>> But the documentation on what that param may look like is missing:
>> http://paxrunner.ops4j.org/display/paxrunner/Start+levels
>>
>> Any help would be appreciated.
>> Andrew
>>
>> _______________________________________________
>> general mailing list
>> general@lists.ops4j.org
>> http://lists.ops4j.org/mailman/listinfo/general
>
>
> _______________________________________________
> general mailing list
> general@lists.ops4j.org
> http://lists.ops4j.org/mailman/listinfo/general
>
>

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to