[MJAR-253] Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.

[jira-importer]

c opened MJAR-253 and commented

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.

 

---

Affects: 3.0.0, 3.0.1, 3.0.2, 3.1.0

Issue Links:

• MJAR-198 jar:jar without classifier replaces default jar
  ("is caused by")

[jira-importer]

Karl Heinz Marbaise commented

Can you please create an example project which shows the use case and could you please explain the whole context of such use case...?

[jira-importer]

Karl Heinz Marbaise commented

So after rereading the description I'm getting the impression you are doing things wrong. If you like to create a zip via maven-assembly you can create different jars by having different modules which produce appropriate jar's which can simply gathered together with an assembly descriptor...The finalName field not the correct way to go...apart from that it will only change the name which is created in the target directory which brings my to the conclusion that you are using a file based assembly descriptor approach...

[jira-importer]

c commented

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 :)

 

[jira-importer]

Karl Heinz Marbaise commented

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..?

[jira-importer]

Karl Heinz Marbaise commented

Unfortunately missing feedback.