Closed foal closed 4 years ago
This is by design to keep things simple (in the plugin). The goal is to make simple things easy and more complex things possible, so the plugin bails out on any kind of possible conflict and let's you fix it:
src/main/resources/META-INF/
so you don't even need any kind of configuration)[INFO] …/src/main/java already added as a resource folder; skipping.
)copy-resources
to copy the license file rather than declaring the project.basedir
as a resource folder.update-project-license
to automatically keep the ${project.basedir}/LICENSE.txt
file up-to-date and put it into the JAR's META-INF/
.That being said, if you think this can easily be implemented, I'll be happy to review a PR.
Thank you! copy-resources
and license:update-project-license
looks reasonable.
I have a project that copies license from project root to the META-INF folder by maven-resource-plugin. The configuration is the same as described in this question https://stackoverflow.com/questions/28619630/copy-a-resource-file-with-maven-located-at-the-root-of-the-project.
But it caused the following warning
and so no sources in produced JAR.