-
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
Gretty 2.3.0 JettyScannerManager error #99
Comments
Thanks for the report. Which JDK and Gradle are you using, and can you please provide a minimal example project. |
I just noticed the same issue. Could it be related to #95? The new Groovy perhaps outputs some broken bytecode because of the compile error? |
@boris-petrov an excellent theory. I have some local commits with a fix in the works for that. If we can document a reproducible case for this, it can be tested (might just rely on |
I already tried jdk 8 and 11. Maybe I will provide the sample project on
monday.
…On November 30, 2018 6:21:41 PM Brett Randall ***@***.***> wrote:
@boris-petrov an excellent theory. I have some local commits with a fix in
the works for that. If we can document a reproducible case for this, it can
be tested (might just rely on scanDir or fastReload).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I can reproduce this also. The problem call is at:
I think this is caused by Groovy bug Statically compiled calls to protected methods of an outerclass' superclass result in IllegalAccessErrors (fixed in Groovy 2.5), together with 3cb2547 which added gretty/libs/gretty/src/main/groovy/org/akhikhl/gretty/scanner/BaseScannerManager.groovy Line 15 in 41d081c
We can either remove that one |
- Fixed #99. - See https://issues.apache.org/jira/browse/GROOVY-7862 . Signed-off-by: Brett Randall <[email protected]>
This is the configuration:
every I changed the content of WebContent the JettyScannerManager throw error
gretty 2.2.0 works properly, no error
The text was updated successfully, but these errors were encountered: