[
https://issues.apache.org/jira/browse/MJAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517901#comment-16517901
]
Karl Heinz Marbaise commented on MJAR-253:
------------------------------------------
As already mentioned can you please an example project as you currently using
it so I can see how you are using the jar plugin / assembly plugin and make
suggestions etc..?
> Since 3.0.0 builds fail with You have to use a classifier to attach
> supplemental artifacts to the project instead of replacing them.
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MJAR-253
> URL: https://issues.apache.org/jira/browse/MJAR-253
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0
> Reporter: J.Cranendonk
> Priority: Minor
>
> See also:
> [https://stackoverflow.com/questions/40964500/maven-jar-plugin-3-0-2-error-you-have-to-use-a-classifier-to-attach-supplementa]
> https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16420958&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16420958
> https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16516772&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16516772
> Builds where multiple jars were created with different names using the
> finalName field (for example to create jars to put together in an assembly)
> are failing since version 3.0.0 of the plugin.
> Apparently cause they now require a classifier field to be set:
> You have to use a classifier to attach supplemental artifacts to the project
> instead of replacing them.
> The problem with fixing this by setting a classifier is that it gets added
> after the finalName field, including a dash, which means the final jar has
> the wrong name.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
