add Maven 3 vs 4 plugins for master switched to Maven 4 #26
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
slawekjaranowski
approved these changes
May 26, 2025
|
There is also - https://github.com/apache/maven-filtering |
|
uh, I did not know: it proves that this is useful (I hate that we're having more Maven subprojects that do a Maven 4 specific branch in parallel to Maven 3 one...) |
cstamas
approved these changes
May 26, 2025
slachiewicz
approved these changes
May 29, 2025
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.
make sure that plugin directories contain by default the Maven 3 branch
and the few plugins that switched to Maven 4 in master are in a separate directory marked "-4"
there are many plugins which are still at Maven 3 in master, but have a non-maintained
mvn4branch: for now, let's ignore them