[
https://issues.apache.org/jira/browse/DELTASPIKE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167611#comment-16167611
]
Jörg Sesterhenn commented on DELTASPIKE-1257:
---------------------------------------------
Thanks for asking, [~struberg]. Please do not remove the BOM - we are really
happy that you introduced it just lately.
We use your BOM to standardize in our company. We have a company POM that every
project is required to use as parent for their projects. In this parent-POM we
set versions for all standardized libraries. That way our developers do not
have to set the versions for these in our products.
We could follow your proposal but that has one big downside for us:
We, the team that maintains this parent-POM follow a lot of libraries like
deltaspike, weld, log4j, slf4j, ... and define the dependencyManagement for all
of their modules. ==> Every release we need to check for all the libraries we
standardized if there are modules that were added, removed, renamed or
relocated. That is something we would really rather not do because it is
cumbersome and error-prone since we know a lot less about your modules than
you. So we would rather have you do this for your modules and provide it as
service to us in your BOM.
Regarding your comment in the mailinglist:
{quote}
Also the boms are really error prone. They ONLY work in the exact pom you
declare them in.
So if you import the bom in your parent project and then reference the various
deltaspike modules only in some specific parts of your build then it doesn't
work anyway. It's just not worth it!
{quote}
I have no idea what you are talking about. Importing a BOM in your Parent POM
is exactly what we are doing at our company and we have never seen the issue
you are describing. Maybe you want to reread the docs on this as they are
really hard to understand:
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
...
Maybe talk to the devs at jboss, weld or log4j they are doing a great job
delivering their BOMs.
> Research why BOM isn't working right in a release
> -------------------------------------------------
>
> Key: DELTASPIKE-1257
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1257
> Project: DeltaSpike
> Issue Type: Task
> Affects Versions: 1.8.0
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 1.8.1
>
>
> https://lists.apache.org/thread.html/655162d82786d1201c2b33a20d82db8a36a642d0d9afc20042584b0d@%3Cdev.deltaspike.apache.org%3E
> Something causes the release to work incorrectly with the BOM not inheriting
> from DS parent.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
