Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MDEPLOY-313] Update to parent 41, cleanup #47

Merged
merged 8 commits into from
Jan 12, 2024
Merged

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented Jan 12, 2024

In general perform a cleanup of plugin, apply updates where needed. The plugin now builds against 3.9.x latest, and minimum is left as is (3.2.5).

A notable change along that above is removal of "baked in" packaging, now plugin relies completely and only on what project and artifact tells, there is no "if this is POM" check anymore. The new "BOM UT" shows this in action. Has to be noted though, that the UT tests ONLY the plugin, to use BOM packaging you need Maven that knows what it is (Maven 3 w/ extension or Maven 4 that has it OOTB).


https://issues.apache.org/jira/browse/MDEPLOY-313

In general perform a cleanup of plugin, apply updates,
where needed. The plugin now builds against latest 3.9.x
and minimum is lifted to 3.6.3.

---

https://issues.apache.org/jira/browse/MDEPLOY-313
@cstamas cstamas self-assigned this Jan 12, 2024
@cstamas
Copy link
Member Author

cstamas commented Jan 12, 2024

This PR incorporates changes from #46 but adds more, supersedes it

pom.xml Outdated Show resolved Hide resolved
pom.xml Outdated Show resolved Hide resolved
@cstamas cstamas merged commit 390e610 into master Jan 12, 2024
58 checks passed
@cstamas cstamas deleted the MDEPLOY-313-take2 branch January 12, 2024 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants