-
Notifications
You must be signed in to change notification settings - Fork 28
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
Not able to define custom manifest entries #13
Comments
PR made |
This enables the plugin to support for example capsule-desktop or other caplets if they need custom manifest entries |
Hmm. Can you add this to your capsule definition and see if it works? It should work in tandem with the task myCapsule(type: FatCapsule){
// ...
manifest {
attributes(GUI: 'true')
}
} |
I tried this but you get a StackOverflowException when you do this. |
Yikes. Can you run gradle with |
|
Thank you. I've tried it on the gradle test setup in the project and it seems to be working. What version of gradle are you using, and if you don't mind, can you paste your capsule definition here? |
I'm using 2.7 and I was trying to implement Capsule in Valkyrie RCP (https://github.com/lievendoclo/Valkyrie-RCP)
|
Dang. I'm not having any luck reproducing the error. I'll have to take a deeper look at it later. In the mean time, you can create a subclass of the CapsuleManifest, override the methods to add in the functionality from your pull request, and call
This should get your project up and running until I have a fix. |
The issue can be reproduced with multi module projects. Making a single submodule and using the plugin in there will trigger the issue.
|
@danthegoodman I actually was able to fix it in my PR by explicitly overriding the manifest method and copying all the code from the Jar task in there. By doing this, it's now possible to use the manifest closure in sub-projects. |
@lievendoclo I was applying your changes and went to add a test. In doing so, I temporarily upgraded my gradle-wrappper.properties file to the latest version and the issue was magically fixed. ✨ After some thorough testing, it looks like the issue stemmed from the compiled groovy classes from one of the earlier groovy-gradle versions conflicting with the groovy-gradle runtime in the later versions. Upgrading to Gradle 2.7 forces the plugin to be run in gradle 2.4+. Instead of trying to work around a bug I don't fully understand, I'd rather upgrade the libraries and avoid the issue altogether. Thank you for your help in tracking this issue down. If people end up asking for gradle <2.3 support, I'll end up using your PR. |
At the moment, you can't define any custom manifest entries
The text was updated successfully, but these errors were encountered: