-
Notifications
You must be signed in to change notification settings - Fork 7
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
CVE-2018-8013 #12
Comments
build-tools is in the support directory. You have to first do a No idea when to do a 3.1.15 release, I'm not using this project any more... And in all my projects I override the batik version anyway... |
Thanks @rototor, that's very helpful. I'll try to build the project locally building the build-tools module first as you suggested. Regarding the override of the batik version I'm afraid that is not working for me :( If I add your dependency
|
What IDE are you using? Are you sure, that the IDE correctly reimported the changed pom.xml? IDEA has sometimes troubles here and as far as I remember Eclipse was even worse... - IDEA has a "Reimport Maven" Action to fix such stuff. This looks like a broken classpath problem to me. |
I'm using IntelliJ, but I'm facing the problem executing my integration tests from maven directly in the console and when I execute the project in Docker, so I'm pretty sure that is something not related to the IDE. Anyway, I'll try to build from the master branch to check if that version of the jeuclid lib do the trick. |
Hello!
Do you have an ETA for the new release
3.1.15
?I've seen that you have bumped batik version to
1.14
in themaster
branch and that would solve the critical security vulnerability CVE-2018-8013.BTW, I've tried to compile the project in my local environment with Java 11 using the command
mvn clean install
and it failed with the next error message:I've searched for that dependency in maven central with no luck.
Does it sound familiar to you?
Thanks in advance!
The text was updated successfully, but these errors were encountered: