-
Notifications
You must be signed in to change notification settings - Fork 261
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
fix maven dependencies version #5930
Conversation
Signed-off-by: Bogdan Sava <[email protected]>
Signed-off-by: Bogdan Sava <[email protected]>
Signed-off-by: Bogdan Sava <[email protected]>
Signed-off-by: Bogdan Sava <[email protected]>
Signed-off-by: Bogdan Sava <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bogdan-sava Can you describe the scenario to demonstrate the original problem - is there a linked issue?
Here I see we are:
- Adding a new dependency for the graph repo connector (scope=compile)
- Adding an exception for our dependency checker (which normally is only needed for scope=runtime)
- Adding spring-boot-starter-validation to server chassis & ui chassis (with exception, but this is normal for spring boot as it's typically runtime)
This has resulted in needing the older hibernate version -- if we have to go with it that's fine - though we should check for outstanding CVEs. But I'd like to also understand the mechanics as I believe the code works as-is with maven, but the problem you are addressing only manifests itself in the intelliJ environment (which is also important to document/have working)
I understand there was an initial loading issue - am I correct that all the above changes were specifically to address this? Is there a reason the ui-chassis is affected since it does not load connectors?
The issue is that while configure IntelliJ with additional maven dependency for running server-chassis-spring with graph-repository-connector, fails with:
Main problem is that |
This is happening because IntelliJ is running the OMAGServerPlatform main class with the following command:
You can run it like this in command line, with same result. But as you can see the hibernate-validator version is 4.3.0. |
The dependency can be runtime. Is it help with check? |
@bogdan-sava @planetf1 I wondered whether an equivalent change needs to be made to gradle or is this not an issue for the gradle build? |
I am proposing to continue the discussion and the review on the security call and see if there is need to threat some aspects proposed by this change separately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve and recommend merging :
- you’ve done investigation of a specific problem with the connector and also looked at the general way things work
- It addresses a real problem for you & the team
- There is a PR ready to go
- I’ve not identified a specific issue during the review - just a feeling of some oddities in IntelliJ/mvn but which could be my understanding. I don’t have any evidence of a problem written up (other than a minor backleveling)
- even if there were to be issues, this doesn't make things any worse.
- There is no justification for further delay.
- Therefore we merge.
- Then, let’s see how it goes.. we still have a week or two in the release. More people will have exposure.
If/when I can document a clear broken path (there may not be one …) I will raise a new issue and we’ll take it from there based on that specific evidence
Approve.
@davidradl ideally we should get gradle to parity - but the gradle build still needs a concerted effort to get to parity. |
Description
server-chassis-spring is not working started in IntelliJ by adding intellij runtime dependency.
:graph-repository-connector brings
:hibernate-validator:4.2.0
via:janusgraph-cql
->:cassandra-all
->:reporter-config3
This version of hibernate-validator is not compatible with spring-boot
Fixed by controlling hibernate-validator version through dependency management