Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 2.2
-
Labels:None
-
Patch Submitted:Yes
Description
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.
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!!!