You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Short description of the issue/suggestion:
Since Gradle will at some point make the config. cache the default, and deprecate disabling it, it would be good to get javapackager to support it. This is by no means a pressing issue.
So far from my limited testing it seems to be from the package tasks referencing the project to dynamically create some tasks to handle work - I believe at least some of these can be handled by injected services, though I do not see a clean way to wire them through to the packager from the task initializer.
I'm submitting a…
Short description of the issue/suggestion:
Since Gradle will at some point make the config. cache the default, and deprecate disabling it, it would be good to get javapackager to support it. This is by no means a pressing issue.
So far from my limited testing it seems to be from the package tasks referencing the project to dynamically create some tasks to handle work - I believe at least some of these can be handled by injected services, though I do not see a clean way to wire them through to the packager from the task initializer.
Steps to reproduce the issue/enhancement:
What is the expected behavior?
Build succeeds
What is the current behavior?
Build fails.
Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information (e.g. related issues, suggestions how to fix, links for us to have context)
The text was updated successfully, but these errors were encountered: