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

[MNG-8180] Handle NPE due non-existent tags #1639

Merged
merged 3 commits into from
Aug 11, 2024
Merged

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented Aug 10, 2024

There was an NPE possibility when plugin.xml had no expected tags present.

Also: maven-compat has plugin.xml (!) w/o "name" tag, it NPEd and failed build. This was NOT picked up by CI as "rebuild itself" step does not install (just verify).


https://issues.apache.org/jira/browse/MNG-8180

@cstamas cstamas self-assigned this Aug 10, 2024
@cstamas cstamas added this to the 4.0.0-beta-4 milestone Aug 10, 2024
@cstamas cstamas changed the title [MNG-8180] Handle NPE due non-existend tags [MNG-8180] Handle NPE due non-existent tags Aug 10, 2024
@gnodet
Copy link
Contributor

gnodet commented Aug 11, 2024

@cstamas should we remove that plugin.xml at the same time ?
The mojos referenced in the plugin.xml do not exist in maven-compat, so I think it's useless.

@cstamas
Copy link
Member Author

cstamas commented Aug 11, 2024

@gnodet yup, we could remove plugin.xml, and am unsure about the rest, as I see in history, they belong together. Also, they are being mention here https://cwiki.apache.org/confluence/display/MAVENOLD/Deterministic+Lifecycle+Planning and to me it seems like those are not even m3 -> m2 backward compat, but in fact m2.1 -> m2.0 (!!!) backward compat thing.

@cstamas
Copy link
Member Author

cstamas commented Aug 11, 2024

but let's do it in separate JIRA IMO

@cstamas
Copy link
Member Author

cstamas commented Aug 11, 2024

@cstamas cstamas merged commit da7c211 into apache:master Aug 11, 2024
13 checks passed
@cstamas cstamas deleted the MNG-8180 branch August 11, 2024 16:56
This pull request was closed.
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.

3 participants