-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
two versions of groovy jars in the classpath #267
Comments
with groovy 2.5.5 removed, sometimes i see this in the log:
|
this is due to some changes in Java 9 as far as I remember, see also: |
i've tried the obvious diff:
but the jar is still packaged in the war regardless:
|
according to https://stackoverflow.com/a/36646805 according to
an update to 2.25.4 was attempted in geonetwork/core-geonetwork#6364 but reverted later on for causing regressions. |
that extra jar breaks geonetwork startup, cf georchestra/ansible#125 (comment)
dont ship an extra version of groovy jar (fixes #267)
that extra jar breaks geonetwork startup, cf georchestra/ansible#125 (comment) (cherry picked from commit 1533f8b)
dont ship an extra version of groovy jar (fixes #267)
dont ship an extra version of groovy jar (fixes #267)
as found out by @pmauduit in georchestra/ansible#125 (comment) the geonetwork war we ship so far has two versions of groovy libs in the classpath:
this prevents GN4 to start with an ugly ton of backtraces in the logs, removing
groovy-2.5.5.jar
from the webapp fixes the issue.The text was updated successfully, but these errors were encountered: