Skip to content

Maven dependencies #200

@mathbagu

Description

@mathbagu

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})

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions