On 12/6/10 9:34, Guillaume Nodet wrote:
What is  FELIXM2 supposed to be ?

As I said in my previous reply to the first post for this issue, it was created a long time ago as a JIRA project for maven-bundle-plugin. It was a mistake that should be removed, but for whatever reason it lives on.

-> richard

On Mon, Dec 6, 2010 at 14:50, Luca Stancapiano (JIRA)<[email protected]>  wrote:
     [ 
https://issues.apache.org/jira/browse/FELIXM2-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Stancapiano updated FELIXM2-12:
------------------------------------

    Description: I think it's a important feature if you can manage the 
maven<optional>  tags in maven-bundle-plugin. The dependencies tagged as optional 
must not be seen as mandatory dependencies when we install a bundle. Second, you don't need 
to configure twice the pom, one for the dependency and one for the bundle-plugin  (was: I 
think it's a important feature if you can manage the maven<optional>  tags in 
maven-scr-plugin. The dependencies tagged as optional must not be seen as mandatory 
dependencies when we install a bundle. Second, you don't need to configure twice the pom, 
one for the dependency and one for the scr-plugin)
        Summary: implementartion for optional tags in maven-bundle-plugin  
(was: implementartion for optional tags in maven-scr-plugin)

implementartion for optional tags in maven-bundle-plugin
--------------------------------------------------------

                 Key: FELIXM2-12
                 URL: https://issues.apache.org/jira/browse/FELIXM2-12
             Project: Felix M2 Plugin
          Issue Type: Improvement
    Affects Versions: 0.1.3
         Environment: maven 3, felix scr
            Reporter: Luca Stancapiano
            Assignee: Timothy Bennett
             Fix For: 0.1.3


I think it's a important feature if you can manage the maven<optional>  tags in 
maven-bundle-plugin. The dependencies tagged as optional must not be seen as 
mandatory dependencies when we install a bundle. Second, you don't need to configure 
twice the pom, one for the dependency and one for the bundle-plugin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.




Reply via email to