arturobernalg opened a new pull request, #13952:
URL: https://github.com/apache/maven/pull/13952
…xecutions
DefaultInheritanceAssembler.mergePluginContainer_Plugins() decided whether a
parent build plugin participates in inheritance with:
element.isInherited() || !element.getExecutions().isEmpty()
so any parent plugin declaring at least one <execution> was folded into the
child's effective plugin set regardless of an explicit
<inherited>false</inherited> - exactly the kind of plugin declaration for which
that flag matters most in practice. Since the default value of isInherited() is
already true, the extra executions clause only ever changed the outcome for
plugins explicitly marked non-inherited, silently overriding them.
Drop the executions override so a plugin's own inherited flag is the only
thing that decides whether it reaches child POMs.
Fixes #7476
Also reproduces on maven-3.9.x (verified against a real 3.9.16 build); happy
to open a backport PR there too if wanted.
---
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](https://www.apache.org/licenses/LICENSE-2.0)
check one of the following:
- [x] I hereby declare this contribution to be licensed under the [Apache
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
- [x] I hereby declare that I have filed an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]