Feature/exclude findbugs annotations #252
Open
Conversation
This file contains 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
|
Thanks a lot. This should fix also a problem I currently have: "javax.annotation" in version 3 from com.google.code.findbugs:jsr305. When will this be ready and available in maven central? |
|
I noticed the same issue in OSGi environment that's the reason why PR is created. I don't know roadmap of json-schema-validator project but I also need the fixed release as soon as possible. |
borcsokj
force-pushed
the
feature/exclude-findbugs-annotations
branch
from
6b67e39
to
36f79e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Excluded Findbugs dependency (similar to Maven provided scope). It is needed to use json-schema-validator in OSGi environment because Findbugs have conflicting Java packages (annotations) and not used at runtime.