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
By default the maven-jar-plugin replaces all JAR file names with the word SNAPSHOT in them with a time stamp. A jar file called myjar-SNAPSHOT.jar will be renamed to myjar-20220409053011.jar (or something like that). This means that the class-path entry inside the generated manifest.mf file will list JAR files that are actually not present in the libs folder, hence they will not be copied to the jdeploy-bundle/libs directory as jdeploy uses the manifest information for the copying.
The text was updated successfully, but these errors were encountered:
I'm going to have to experiment a little bit to find the exact combination of parameters in the maven dependencies/maven jar plugin that results in this. I use those plugins and this behaviour doesn't seem to happen for me.
In any case, when it happens, it does make sense the jDeploy should print out a warning - and we should document this in a troubleshooting section.
By default the maven-jar-plugin replaces all JAR file names with the word SNAPSHOT in them with a time stamp. A jar file called myjar-SNAPSHOT.jar will be renamed to myjar-20220409053011.jar (or something like that). This means that the class-path entry inside the generated manifest.mf file will list JAR files that are actually not present in the libs folder, hence they will not be copied to the jdeploy-bundle/libs directory as jdeploy uses the manifest information for the copying.
The text was updated successfully, but these errors were encountered: