Downgrade org.reflections to 0.9.11 due to a bug #161
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Apparently I'm able to invoke our codepropertygraph's console via a path that triggers ronmamo/reflections#273. This is very unfortunate and due to the way the artifact is being published I'm unable to downgrade directly in the project I use. Sadly this dependency is propagated very far down the chain and it impossible to untangle it. The fix is in 0.9.13-SNAPSHOT (not yet released) so suggesting to downgrade until it is officially out.
hubertp
force-pushed
the
hubert/downgrade-reflections
branch
from
3fb1c72 to
8272864
Compare
Contributor
Author
|
Replaced with #162 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apparently I'm able to invoke our codepropertygraph's console via a path
that triggers ronmamo/reflections#273.
This is very unfortunate and due to the way the artifact is being
published I'm unable to downgrade directly in the project I use.
Sadly this dependency is propagated very far down the chain and it
impossible to untangle it.
The fix is in 0.9.13-SNAPSHOT (not yet released) so suggesting to
downgrade until it is officially out.