general  

[issues] Commented: (PAXCONSTRUCT-127) Support for specifying start level for modules

clifford james (JIRA)
Sun, 24 Jan 2010 17:41:29 -0800

    [ 
http://issues.ops4j.org/browse/PAXCONSTRUCT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13296#action_13296
 ] 

clifford james commented on PAXCONSTRUCT-127:
---------------------------------------------

I just ran into this shortcoming today.  I don't think it's "Un Maven-like" to 
have a separate file for additional meta-data.  For example, look at the 
"assembly.xml" that the maven-assembly plugin uses.  We don't even have to have 
an XML file.  Something like this:

foo/bar/artifa...@1
foo/bar/artifa...@nostart

in a text file would work.  Although the lack of XML probably is un Maven-like 
;-)

I actually don't see why these can't be duplicates since it's a seperation of 
concerns: pom.xml is for deps and bundle-config.xml (or whatever you want to 
call it) is for specifying bundle configurations that override the default (all 
bundles started at start leve 5).

> 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