You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the above configuration and execution, the resulting JAR name under target/ is: xxxxxxx-shaded-obfuscated.jar
While the installed JAR (under .m2) name is: xxxxxxx-obfuscated.jar
The expected behavior is that in both cases the name would be: xxxxxxx-obfuscated.jar
(as it's based on the ${project.build.finalName} with an addition of attachArtifactClassifier value.)
So, the erroneous behavior is that the classifier is appended to the injar named file, instead of the project main artifact name.
Affected version of the plugin: 2.2.0. (Same happens also with 2.0.14.)
The text was updated successfully, but these errors were encountered:
wheredevel
changed the title
The name of the "proguarded" JAR under target/ is different from the one installed.
The name of the "proguarded" JAR under target/ is different from the one installed under .m2.
Mar 29, 2020
Here's the portion of the plugin configuration:
Here's the portion of the plugin execution:
With the above configuration and execution, the resulting JAR name under target/ is:
xxxxxxx-shaded-obfuscated.jar
While the installed JAR (under .m2) name is:
xxxxxxx-obfuscated.jar
The expected behavior is that in both cases the name would be:
xxxxxxx-obfuscated.jar
(as it's based on the ${project.build.finalName} with an addition of
attachArtifactClassifier
value.)So, the erroneous behavior is that the classifier is appended to the
injar
named file, instead of the project main artifact name.Affected version of the plugin: 2.2.0. (Same happens also with 2.0.14.)
The text was updated successfully, but these errors were encountered: