Open mkroening opened 5 years ago
I have the same problem, gradle run
fail ("Package test.main.asset not found in module"), but gradle installDist
generate a working application.
If it can help, I made a minimal test project for this issue: https://github.com/Ealrann/gradleTestResourcePackage.git
Edit: Ok, I forgot about that, but there is already an issue about this topic on the gradle github: https://github.com/gradle/gradle/issues/4733
I've seen this too. I'm not sure if this is an issue with this plugin or something else. Happy to accept a PR to fix this issue.
I need to open up a resource package not containing any classes, but the run task fails. Running the build task and then executing the distribution will work.
A workaround is creating a dummy class in the package.
I stumbled onto this bug while experimenting with OptaPlanner on the module path: https://github.com/mwkroening/optaplanner-modulepath-example/pull/2
I also modified the test-project to show this behaviour: https://github.com/mwkroening/gradle-modules-plugin/commit/48c57939d4b0aea64c3a071d2f149ff62a123538 Running
$ ../gradlew :greeter.runner:run
will fail, but$ ../gradlew :greeter.runner:build
and then executing the distribution succeeds.