-
Notifications
You must be signed in to change notification settings - Fork 393
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
control which jar is added last (or first) so the correct MANIFEST.MF is present #21
Comments
Do you have an example project for this? So if you have a project
then that Manifest will be in the Shadow jar. However, if you're aren't defining a manifest file in your project, then it's going to include whichever manifest file it encounters first while processing the dependency jars. |
However, there is some additional work that needs to be done to the filtering to make them easier to use. Layering various excludes/includes at different levels doesn't always work the greatest. |
I'm currently using it to build JFXtras (http://jfxtras.org/), source are in github (link is on the webpage). I have not tried using the jar thingy, I'm a Gradle newbie, I do have a MANIFEST.MF file in the resource directory. Tom On 2013-12-11 21:39, John Engelman wrote:
|
Thanks. The jar task worked! On 2013-12-11 21:39, John Engelman wrote:
|
Right now I have two jars, each with a MANIFEST.MF and a MANIFEST.MF in my src/main/resources/META-INF directory. It cannot control which MANIFEST.MF end up in the shadow.jar. Ideally it per default should be the one in my src directory.
The text was updated successfully, but these errors were encountered: