Open marschall opened 10 months ago
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, "I'm eager to make a meaningful contribution to this codebase and help resolve any issues that may arise."
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.