Skip to content
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

Maven dependencies #200

Open
mathbagu opened this issue Jan 16, 2017 · 0 comments
Open

Maven dependencies #200

mathbagu opened this issue Jan 16, 2017 · 0 comments

Comments

@mathbagu
Copy link
Contributor

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})
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant