Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Incomplete
-
2.0.4
-
None
-
None
Description
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:
// 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 ) {
Attachments
Issue Links
- is related to
-
MSOURCES-10 Attached source artifact should not be added for artifacts with classifier
- Closed
-
MNG-5384 Declarative artifacts
- Open
-
MNG-2650 Classifiers are not powerful enough to adress the problem of generating different flavours of an artifact
- Closed