Hi dev list, I just found this strange behavior when I was looking at the fingerprints of jars generated by a Maven Java project and I wanted to share it with you to see what you think of it.
My Jenkins maven project is using the maven-shade-plugin <http://maven.apache.org/plugins/maven-shade-plugin/> (2.1 or 2.3) with default configuration. it generates 2 jars: - myproject-1.0.0.jar: the shaded jar which is attached to the build (default behavior of the maven-shade-plugin) - original-myproject-1.0.0.jar: the jar which is generated by the maven-jar-plugin and renamed by the maven-shade-plugin. This jar is not attached to the build. When I check the archived artifacts of the Jenkins build, I can see that it is the shaded jar (myproject-1.0.0.jar) but with the md5sum of the original jar (original-myproject-1.0.0.jar) What's your opinion on it? Is it a Jenkins bug? For your information, setting the property shadedArtifactAttached to true attach the 2 jars to the build and Jenkins don't mismatch the fingerprints. Regards -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
