Add EJB dependency only as JavaDoc dep. #449
Merged
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
|
An attempt to fix CI is part of #450 |
starksm64
approved these changes
Sep 16, 2020
manovotn
added a commit
to weld/core
that referenced
this pull request
Sep 17, 2020
rhusar
pushed a commit
to rhusar/weld-core
that referenced
this pull request
Apr 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recent merge of some of the missing changes from 3.0 branch caused re-introduction of EJB dependency when it is only really needed for Javadoc. I have bumped into this when building a shaded jar javadoc containing CDI API which now requires me to add EJB dep as well.
This PR removes EJB dep and only introduces it as additional javadoc dependency.