In a MAVEN multi-module project, when you do unified versioning, you typically define the Dependencymanagement node in the parent Pom file, which declares the dependencies node content for a unified, defined version of the resource, defined directly by the The resources in the Dependencies node do not need to introduce version-related content, for example, the following:
<dependencyManagement> <dependencies > <dependency > <groupId>com.devzuz.mvnbook.proficio</groupId> <artifactId>proficio-model</artifactId> <c>${project.version}</version> </dependency > <dependency > <groupid>com.devzuz.mvnbook.proficio</groupid > <artifactid>proficio-api</artifactid > <version>${project.version}</version >&nbsP </dependency > <dependency > <groupId> com.devzuz.mvnbook.proficio</groupid> < artifactid>proficio-core</artifactid> <version>${project.version}</version> </ dependency > <dependency > <groupId>com.devzuz.mvnbook.proficio</groupId> <artifactid>proficio-store-memory</artifactid > <version>${project.version}</version >