[
https://issues.apache.org/jira/browse/DELTASPIKE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259977#comment-15259977
]
Jörg Sesterhenn commented on DELTASPIKE-1088:
---------------------------------------------
https://issues.jboss.org/browse/WELD-2115 has been fixed in the meantime.
So now there is another great example: [the weld
BOM|http://repo1.maven.org/maven2/org/jboss/weld/weld-core-bom/2.3.4.Final/weld-core-bom-2.3.4.Final.pom].
If there are any questions I might answer feel free to ask.
Please consider this change for your next release since it is little trouble
and of great value to your users.
> Provide a BOM for deltaspike with no transitive dependencies
> ------------------------------------------------------------
>
> Key: DELTASPIKE-1088
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1088
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.5.4
> Reporter: Jörg Sesterhenn
> Assignee: Mark Struberg
>
> We have an enterprise parent POM that defines versions of maven artifacts for
> all products that are built in our enterprise.
> We want to define the version of all deltaspike artifacts in that parent pom.
> Idealy we would just import your BOM.
> Currently your BOM inherits a bloat of dependencies from the deltaspike
> parent POM. We don't want all of these transitive dependencymanagement
> entries in our parent POM.
> So instead of importing your BOM we copy the entries for all deltaspike
> modules into our parent POM. This is a violation of DRY / cumbersome / error
> prone...
> Please provide a BOM that does not inherit any other dependencymanagement.
> One example of a great BOM is [the log4j
> BOM|http://central.maven.org/maven2/org/apache/logging/log4j/log4j-bom/2.5/log4j-bom-2.5.pom].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
