Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <483280258.1251909872867.JavaMail.jira@brutus>
Date: Wed, 2 Sep 2009 09:44:32 -0700 (PDT)
From: "Stuart McCulloch (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Resolved: (FELIX-1021) Classifier always used even if not
 explicitly set in the configuration
In-Reply-To: <2056028776.1238584273134.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stuart McCulloch resolved FELIX-1021.
-------------------------------------

    Resolution: Fixed

Fixed in r810600.

> Classifier always used even if not explicitly set in the configuration
> ----------------------------------------------------------------------
>
>                 Key: FELIX-1021
>                 URL: https://issues.apache.org/jira/browse/FELIX-1021
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.0.0
>         Environment: Maven 2.1.0
>            Reporter: Guillaume Durand
>            Assignee: Stuart McCulloch
>             Fix For: maven-bundle-plugin-2.0.1
>
>
> If I build a bundle specifying a classifier in the command line, this classifier is used even if I did not explicitly used the classifier property in the bundle configuration. This is not consistent with the jar plugin for instance, which requires the classifier property to be set in the plugin configuration in order to really use the classifier.
> This behaviour is very problematic for by builds because I use parent projets to build several child projects, some of which needing a classifier (typically bundles containing native code). With the current behaviour, if I build the parent project with classifier linux-x86, all the bundles (even pure java bundles) will be classified. This is not wanted.
> With previous versions of maven I could set a classifier property in the pom file to null when I did not want the classifier for a particular bundle, but now this workaround no longer works.
> To fix the problem replace in BundlePlugin.java:
> * @parameter expression="${classifier}"
> */
> protected String classifier;
> with 
> * @parameter
> */
> protected String classifier;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.