[
http://jira.codehaus.org/browse/MNG-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120182
]
Michael Semb Wever commented on MNG-2596:
-----------------------------------------
I gather the following is related?
http://docs.codehaus.org/display/MAVENUSER/Expanded+Classifier+Support
(
http://216.239.59.104/search?q=cache:D39KuRCONdQJ:docs.codehaus.org/display/MAVENUSER/Expanded%2BClassifier%2BSupport+Expanded+Classifier+Support&hl=en&ct=clnk&cd=1&client=firefox-a
)
> Allow support for multiple classifier for a given artifact
> ----------------------------------------------------------
>
> Key: MNG-2596
> URL: http://jira.codehaus.org/browse/MNG-2596
> Project: Maven 2
> Issue Type: New Feature
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Vincent Massol
> Fix For: Reviewed Pending Version Assignment
>
>
> Right now Maven 2.0.x only support a single classifier per artifact. There
> are cases where more than 1 classifer would be required. For example the
> Clover plugin modifies the current artifact to add a "clover" classifier.
> However when the source plugin runs it tries to add another classifier
> ("sources") to the artifact. As only one classifier is currently supported
> it's not working (see MSOURCES-10). In the clover plugin code we also have
> things like:
> {code:java}
> // Do not try to find Clovered versions for artifacts with
> classifiers. This is because Maven2 only
> // supports a single classifier per artifact and thus if we replace
> the original classifier with
> // a Clover classifier the artifact will fail to perform properly as
> intended originally. This is a
> // limitation.
> if ( artifact.getClassifier() == null )
> {
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
