-
Notifications
You must be signed in to change notification settings - Fork 612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a bill of materials (BOM) POM #1503
Comments
If both dependencies should have the same version, you can also use properties: <properties>
<eclipse-collections.version>11.1.0</eclipse-collections.version>
</properties>
<dependencies>
<dependency>
<groupId>org.eclipse.collections</groupId>
<artifactId>eclipse-collections-api</artifactId>
<version>${eclipse-collections.version}</version>
</dependency>
<dependency>
<groupId>org.eclipse.collections</groupId>
<artifactId>eclipse-collections</artifactId>
<version>${eclipse-collections.version}</version>
</dependency>
</dependencies> |
Hello sir, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice if the project provided a Bill of Materials (BOM) POMs that contain all the artifacts of the project.
Many projects like Spring and JUnit provide BOM POMs so that versions have to be specified only once.
Right now if somebody wants to use Eclipse Collections the version has to be specified twice.
With a BOM POM the version has to be specified only once.
It is a bit more verbose. There are other solutions for this like properties. Using BOM POMs is completely optional to users.
The text was updated successfully, but these errors were encountered: