felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Work started] (FELIX-4591) add the ability to specify the classifier in the new baseline configuration of the plugin.
Date Thu, 21 Aug 2014 10:01:17 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Work on FELIX-4591 started by Carsten Ziegeler.

> add the ability to specify the classifier in the new baseline configuration of the plugin.
> ------------------------------------------------------------------------------------------
>
>                 Key: FELIX-4591
>                 URL: https://issues.apache.org/jira/browse/FELIX-4591
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.5.0
>            Reporter: Jonathan DELAIRE
>            Assignee: Carsten Ziegeler
>             Fix For: maven-bundle-plugin-2.5.1
>
>
> The new baselining feature is nice, unfortunately it compare to a specific version without
the option to compare specific classifier, if we don't generate an OSGi bundle by default
it doesn't work.
> For example I'm working on a project that is generating NetBeans modules and OSGi bundle
for the same artifact.
> But since the OSGi bundle is generated as <classifier>bundle</classifier>
and the baseline feature only compare the jar generated by the project default packaging (which
in this case is a jar without the packageinfo and with a netbeans module manifest) so the
baselining fail.
> Adding the ability to specify the classifier in the plugin configuration would be good.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message