[
https://issues.apache.org/jira/browse/MJAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957245#comment-17957245
]
Matthias Bünger commented on MJAR-170:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#335|https://github.com/apache/maven-jar-plugin/issues/335].
> please add property 'maven.jar.classifier'
> ------------------------------------------
>
> Key: MJAR-170
> URL: https://issues.apache.org/jira/browse/MJAR-170
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.4
> Reporter: ryenus
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 2.5
>
>
> For maven-source-plugin, adding a classifier to the source jar file name is
> as simple as:
> # setup property
> <maven.source.classifier>jdk6-sources</maven.source.classifier>
> # setup the right version of Maven source plugin, e.g. version 2.2.1
> And that's enough.
> But to add a classifier to the binary jar file name, we must use the very
> verbose way of configuring the maven-jar-plugin, as below:
> {code:xml}
> <plugin>
> <artifactId>maven-jar-plugin</artifactId>
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal>jar</goal>
> </goals>
> <configuration>
> <classifier>jdk6</classifier>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> By adding support for the {{maven.jar.classifier}} property, it would be much
> more straightforward and consistent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
