Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNAPSHOT Jar files are not deployed when using maven-jar-plugin #60

Open
dlemmermann opened this issue Apr 9, 2022 · 3 comments
Open

Comments

@dlemmermann
Copy link

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.

@dlemmermann
Copy link
Author

This can be prevented by specifying false in the configuration of the maven jar plugin.

@dlemmermann
Copy link
Author

I would propose to add this to the documentation and / or print out a warning.

@shannah
Copy link
Owner

shannah commented Apr 10, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants