maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer W (JIRA)" <>
Subject [jira] Commented: (MSOURCES-50) Add optional 'classifier' for source artifact
Date Mon, 28 Jun 2010 08:55:32 GMT


Rainer W commented on MSOURCES-50:

I have a Testing Project which contains Classes for JUnit > 4.4. So I created a profile
which allows me to set the classifier on the maven-jar plugin. Works fine, except the source
Packaging has still this open Issue. 

The worst part is: when I first run a normal package, and afterwards the Profile with the
classifiert. The jar plugin creates a correct classified jar file. But the source plugin overwrites
my normal sources jar, because it dosn't support classifiers!!!

> Add optional 'classifier' for source artifact
> ---------------------------------------------
>                 Key: MSOURCES-50
>                 URL:
>             Project: Maven 2.x Source Plugin
>          Issue Type: New Feature
>            Reporter: Barry Pitman
>             Fix For: 2.2
>         Attachments: classifier.patch
> The default classifiers, 'sources' and 'test-sources' are sufficient for most cases,
but I have come across cases where specifying a different classifier could be useful. E.g.
when building a skinny war with packaged classes, the 'sources' artifact is really the source
of the (secondary) classes artifact, not the primary war artifact. As such, the classifier
of the sources should be 'classes-sources', not 'sources'.
> I've attached a basic patch which I am using.  

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