-
Notifications
You must be signed in to change notification settings - Fork 36
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
Bug: HotReload Exception with Composite Build #104
Comments
Thanks for the report. Can you:
|
Thanks for the fast reply. I have:
|
I think this was introduced by 1531ea0, which was replacing the deprecated |
I think this is the actual problem, see also https://stackoverflow.com/questions/47910578/not-able-to-copy-configurations-dependencies-after-upgrading-gradle-plugin-for-a?rq=1 Solutions there point out to use compileClasspath instead or to extend an own configuration from implementation. I don't know which approach is better for the future, so it doesn't break again with newer Gradle versions:
I hope it gets fixed with the next gretty version 2.3.2. Thank you. |
Same problem here with a "simple" multi-project build (Gradle 5.1.1, gretty-gradle-plugin 2.3.1, task "appRun") when changing the code in one of the projects and doing a "./gradlew build". Complete stacktrace:
Our workaround is, to go back to gretty-gradle-plugin 2.1.0 and convert "implementation" dependencies to "compile". |
1531ea0 introduced two changes in The second one (on L#155) is wrong and can be fixed by replacing For the first one (on L#77): I don't really understand it (yet). The other changes introduced with 1531ea0 look good to me. |
Now that my PR finally passed travis-ci, it would be great if could make progress here. |
We are coming to the limits of our workaround for this problem. |
We need to migrate within the next 3 month. I need a statement whether gretty will be developed on and this bug will be solved or not. It's the base for our decision whether to stay with gretty or try to find another solution that works for us. |
Hey, any updates for this bug, I faced the same problem? |
@fokkoru JDK, Gradle, Gretty and Container versions please. |
Gretty v. 3.0.1, servletContainer = "jetty9.3"
|
Hey, @javabrett, any luck finding this bug, can I help you with it? |
Manually tested the Pull Request, see #113 (comment) |
Fix issue #104 - Bug: HotReload Exception with Composite
CompositeBuildGrettyExample.zip
Hi,
using
a composite build structure throws Exception upon hot reload of my WebApp after continues build recompiles the lib. I included an example project structure (see .zip) to reproduce:
Please fix as I need this feature for our development with shared/distributed libraries. At the moment we are using the 'old' original Gretty plugin as we are still at JDK 7 there but once we completly switch to JDK 8 and Tomcat 8.5 we need the official as the 'old' one doesn't support newer Tomcats.
Thank you very much! Regards,
gbalthasar
The text was updated successfully, but these errors were encountered: