gnodet opened a new pull request, #13264: URL: https://github.com/apache/maven/pull/13264
The existing warning message `"BOM imports from within reactor should be avoided"` is opaque: it doesn't identify which BOM triggered it, doesn't explain why, and gives no actionable guidance. This PR improves the message to: - Include the BOM coordinates (`g:a:v`) so the user knows which import is affected - Explain the actual risk: the BOM is evaluated in `CONSUMER_DEPENDENCY` mode, which skips conditional profile activation (file/property/condition activations), potentially producing an incomplete `dependencyManagement` compared to the BOM's own `BUILD_PROJECT` build - Suggest the preferred alternative (parent POM inheritance) Example new message: ``` [WARNING] BOM import 'org.jdbi.internal:test-bom:1-SNAPSHOT' references a module within the same reactor. The BOM will be evaluated without conditional profile activation (file/property/condition), which may produce an incomplete dependencyManagement compared to the BOM's own build. Prefer parent POM inheritance for intra-reactor version management. ``` Note: the ordering issue that was the main practical concern (BOM excluded from `-am` subset) is now fixed by #13040. -- 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]
