maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <>
Subject [jira] Commented: (MNG-2596) Allow support for multiple classifier for a given artifact
Date Fri, 10 Aug 2007 14:29:13 GMT


Paul Gier commented on MNG-2596:

Can this be handled by just appending to the existing classifier?  I don't think Maven prevents
you from having a classifier "clover-sources".  It seems like it would have the same effect
as having multiple classifiers, but works with the current implementation.  Any plugins that
modify the classifier would just have to append to it instead of replacing it.

> Allow support for multiple classifier for a given artifact
> ----------------------------------------------------------
>                 Key: MNG-2596
>                 URL:
>             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
> {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:
For more information on JIRA, see:


View raw message