Skip to content

Require Maven 3.6.3+ from plugins#520

Merged
slachiewicz merged 1 commit intomasterfrom
mvn363
Nov 24, 2025
Merged

Require Maven 3.6.3+ from plugins#520
slachiewicz merged 1 commit intomasterfrom
mvn363

Conversation

@slachiewicz
Copy link
Member

A secure version that almost all of our plugins have.

While we agreed that plugins may require Maven 3.9 - I'm not proposing it to not break all our builds

@slachiewicz slachiewicz added the breaking Pull requests that break existing features label Nov 23, 2025
<id>drop-legacy-dependencies</id>
<properties>
<!-- If you MUST depend on any of these, set this to "false", but we WILL come after you! -->
<drop-legacy-dependencies.include>true</drop-legacy-dependencies.include>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we should enable this profile by default, by add property rop-legacy-dependencies.include with true value

@slachiewicz
Copy link
Member Author

I've enabled it locally but so far not too many visible effects - maybe more and more is already upgraded

@slachiewicz slachiewicz merged commit a947913 into master Nov 24, 2025
10 checks passed
@slachiewicz slachiewicz deleted the mvn363 branch November 24, 2025 07:18
@github-actions github-actions bot added this to the 46 milestone Nov 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking Pull requests that break existing features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants