gnodet commented on PR #12417:
URL: https://github.com/apache/maven/pull/12417#issuecomment-4934314059
Closing this PR — thanks for the effort @Hiteshsai007, and the pain point is
well understood.
After review, we've concluded that extending `<scope>import</scope>` to also
inherit properties is not the right approach. It would introduce property
pollution (typical BOMs define hundreds of internal properties), fragile
ordering dependencies between BOMs, and blur the well-established separation
between parent inheritance and BOM imports.
Maven 4 already provides **mixins** (4.2.0+) as the proper mechanism for
this use case. Mixins give you explicit, selective inheritance of properties
(and the full model) with clear semantics — without overloading BOM import
behavior:
```xml
<mixins>
<mixin>
<groupId>com.company</groupId>
<artifactId>company-bom</artifactId>
<version>1.0.0</version>
</mixin>
</mixins>
```
See the earlier review comment for the full analysis. If you're interested
in continuing to contribute, improving mixin documentation or integration test
coverage would be very welcome.
--
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]
