[
https://issues.apache.org/jira/browse/WICKET-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262572#comment-16262572
]
Emond Papegaaij commented on WICKET-6500:
-----------------------------------------
This is also what we do at the moment. A bom like this could replace 51 lines
in one of our parent poms. It's not that you can't do without a bom, but it's a
convenience.
> Publish a wicket-bom artifact GAV
> ---------------------------------
>
> Key: WICKET-6500
> URL: https://issues.apache.org/jira/browse/WICKET-6500
> Project: Wicket
> Issue Type: Wish
> Components: release
> Affects Versions: 8.0.0-M8
> Reporter: Darryl L. Miles
> Priority: Minor
>
> There are many JARs with the entire version suite. It would help consumers
> to manage elements that are released as a single versioned set to be included
> in a BOM.
> This is a maven pom only project, that is designed to be consumed like:
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.apache.wicket</groupId>
> <artifactId>wicket-core-bom</artifactId>
> <version>8.0.0-M8</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> Because the published bom project contains every individual GAV that is
> published for an entire version set inside a <dependencyManagement> .
> Then there should be a snipper in all the Quick Start guides and all example
> projects to use this method by default to introduce / manage version numbers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
