[
http://issues.ops4j.org/browse/PAXCONSTRUCT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998#action_12998
]
Alin Dreghiciu edited comment on PAXCONSTRUCT-127 at 10/5/09 9:43 PM:
----------------------------------------------------------------------
@Stuart
I think the first thing that Pax Construct should do is to use a different way
then the pom scanner when starting Pax Runner.
In my view simpler, easier way, is that Pax Construct will generate a simple
test file that can be read with scan-file:. This one allows specification of
start level per provisioning url where the scan-pom will not because the
reasons you mentioned.
Now regarding how one could specify the start level and / or a bundle to be
started or not cant we use the approach they have in dependency plugin?
For example:
{code}
<configuration>
<artifactItems>
<artifactItem>
<groupId>foo</groupId>
<artifactId>bar1</artifactId>
<startLevel>10</startLevel>
<start>false</start>
</artifactItem>
<artifactItem>
<groupId>foo</groupId>
<artifactId>bar2</artifactId>
<startLevel>2</startLevel>
</artifactItem>
</artifactItems>
<configuration>
{code}
was (Author: adreghi...@gmail.com):
@Stuart
I think the first thing that Pax Construct should do is to use a different way
then the pom scanner when starting Pax Runner.
In my view simpler, easier way, is that Pax Construct will generate a simple
test file that can be read with scan-file:. This one allows specification of
start level per provisioning url where the scan-pom will not because the
reasons you mentioned.
Now regarding how one could specify the start level and / or a bundle to be
started or not cant we use the approach they have in dependency plugin?
For example:
{code}
<configuration>
<artifactItems>
<artifactItem>
<groupId>foo</groupId>
<artifactId>bar1</artifactId>
<startLevel>10</startLevel>
<start>false</start>
</artifactItem>
<artifactItem>
<groupId>foo</groupId>
<artifactId>bar2</artifactId>
<startLevel>2</startLevel>
</artifactItem>
</artifactItems>
<configuration>
{code}
> Support for specifying start level for modules
> ----------------------------------------------
>
> Key: PAXCONSTRUCT-127
> URL: http://issues.ops4j.org/browse/PAXCONSTRUCT-127
> Project: Pax Construct
> Issue Type: Improvement
> Components: maven-pax-plugin
> Affects Versions: 1.4
> Reporter: Kristoffer Peterhänsel
> Assignee:
>
> I am in a position where I need one of my bundles to start early to set up
> some things in Config Admin. Unfortunately it seems impossible to get Pax
> Construct to run a bundle - that is part of the build - at a specific start
> level.
> I have a Pac Construct-created Maven project with a number of sub-modules.
> And one of those I am trying to get to run at start level 2, while everything
> else runs at 5. I can add it in the provision section of my POM as mvn: url
> and get it written into the config.ini (I am using Equinox as OSGi
> framework). But the module dependency will also be written into the file. And
> it appears that the last one will take priority under Equinox.
> So it might be an idea to remove duplicated from the list of bundles to
> provision, to allow this type of overwriting. Alternatively there should be
> some support for having a bundles start level in its POM file. But then I
> guess the issue is Pax Runner related.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
