[jira] [Commented] (FELIX-4591) add the ability to specify the classifier in the new baseline configuration of the plugin.

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105265#comment-14105265 ] 

Carsten Ziegeler commented on FELIX-4591:
-----------------------------------------

I've committed a patch with rev 1619332, it adds the config "comparisonClassifier", so something like
<comparisonClassifier>myClassifier</comparisonClassifier>
should do the trick.

[~jdelaire] Could you please give this a try?

> 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)