`--package` not working with Gradle 5.0
See original GitHub issueRunning the package option with gradle 5.0 installed causes it to fail with the underlying gradle message.
Gradle does not allow passing null for the configuration action for CopySpec.from()
Note that the message was captured debugging.
With gradle 4.10.2, it worked fine.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:14 (4 by maintainers)
Top Results From Across the Web
`--package` not working with Gradle 5.0 · Issue #197 - GitHub
Running the package option with gradle 5.0 installed causes it to fail with the underlying gradle message. Gradle does not allow passing ...
Read more >Troubleshooting builds - Gradle User Manual
If you followed the installation instructions, and aren't able to execute your Gradle build, here are some tips that may help. If you...
Read more >Upgrading your build from Gradle 4.x to 5.0
Try running gradle help --scan and view the deprecations view of the generated build scan. If there are no warnings, the Deprecations tab...
Read more >Upgrading your build from Gradle 5.x to 6.0
Try running gradle help --scan and view the deprecations view of the generated build scan. Deprecations View of a Gradle Build Scan. This...
Read more >Gradle 5.0 Release Notes
The Gradle team is excited to announce Gradle 5.0. ... Configure project and source package names ... 164 issues have been fixed in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
danthegoodman/gradle-capsule-plugin#39 seems to work only with gradle 5 and not with older gradles, otherwise I’d just fork the PR and push it to jcenter as a quickfix. But this option does not seems on the table, because at least gradle 4 should be supported by the plugin.
For sure the best solution would be to implement packaging in-process without calling an external tool. This would also remove the dependency on the capsule-gradle-plugin. Maybe capsule could be called programmatically? I would be very thankful for any help on such a feature.
Alternatively with the new bootstrap header support contributed with #199 we could also think about dropping
--packaging
entirely? IMHO both are a bit too different, so it may be nice to maintain both packaging modes separately.I have published the new plugin, i’m just awaiting for approval, after that i’ll open a PR here to fix the problem 😄