Remove dependency on JTA API #609
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
|
I have also noticed that we are declaring EJB API dependency directly inside maven javadoc plugin. |
|
Sounds like a good idea, but I wouldn't mind if we got rid of the EJB dependency as well :-) |
Ladicek
approved these changes
May 16, 2022
|
Not merging yet, as I assume we'll wanna discuss this on the CDI call tomorrow. |
Yeah, that's exactly what I wanted to bring up in the meeting tomorrow |
arjantijms
approved these changes
May 16, 2022
|
Thanks! |
Emily-Jiang
approved these changes
May 17, 2022
starksm64
approved these changes
May 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Fixes #608
This is one of the ways to address it as we don't really need the dependency on JTA apart from javadoc of a single class.
(FYI @arjantijms)