A lot of maven dependencies are defined inside each module. Sometimes the version of these dependencies are not consistent with the parent pom.xml.
Every module should be checked to ensure that:
- the dependency is required and has the correct scope
- the dependencies are sorted by scope (compilation/runtime/test) and by name (groupId/artifactId)
- the dependency version is defined in the parent pom.xml
- the ipst-core dependencies are referenced with an explicit groupId (eu.itesla_project)
- the (internal) ipst dependencies are referenced with variables (${project.groupId} and ${project.version})
A lot of maven dependencies are defined inside each module. Sometimes the version of these dependencies are not consistent with the parent pom.xml.
Every module should be checked to ensure that: