[
https://issues.apache.org/jira/browse/MJAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517880#comment-16517880
]
J.Cranendonk commented on MJAR-253:
-----------------------------------
Wrong is a big word, but uncommon possibly :)
The artifact is a zip containing files in a distribution format suitable for
our customer.
I can't create the jar's in sub modules, because they require data/dependencies
from the module which creates the zip.
The jar's themselves do not become artifacts, they are not uploaded on
install/deploy/release, they are included in the zip.
We just want to use the jar plugin to create some different jars, in our case
actually to hold some classpath information in the metadata :)
But I see a workaround in using the assembly plugin to rename the jars, that
should work, so I will try that.
It might be a cleaner way do achieve the same result :)
> 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)
