Move components to JSR330 #3325
Open
+26
−11
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
Test Results 588 files 588 suites 3h 41m 15s ⏱️ For more details on these failures, see this check. Results for commit 83ed106. ♻️ This comment has been updated with latest results. |
|
After giving a thought to this one, if we start with core component we will have to preserve both plexus and jsr330 annotations so plexus components in the rest of codebase can find it. |
|
It should be possible to mix things, so we can just start with one component at a time (leaving mojos as is for now). |
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.
See https://github.com/eclipse/sisu.plexus/wiki/Plexus-to-JSR330