OParent deps not downloaded by children

When compiling a project that use OParent as parent project, despite
the usage of ONAP nexus repositories in the project repositories
configuration, the dependencies of org.onap.oparent:oparent are only
searched on maven central which results in build failure for those
projects.

Issue-Id: INT-128
Change-Id: Iba9b92cc563685ffe9454d824191028b357bc9f1
Signed-off-by: Anaël Closson <ac2550@intl.att.com>
1 file changed
tree: 67c9a34e2ad6ca79c3b0c820b1468ada7e9e0248
  1. checkstyle/
  2. license/
  3. oparent/
  4. version-check-maven-plugin/
  5. .gitattributes
  6. .gitignore
  7. .gitreview
  8. LICENSE.txt
  9. pom.xml
  10. README.md
  11. settings.xml
  12. version.properties
README.md

ONAP O-Parent

Description

ONAP O-Parent provides common default settings for all the projects participating in simultaneous release.

  • Isolate all the common external dependencies, default version, dependency management, plugin management, etc.
  • Avoid duplicate/conflicting settings for each project
  • Each project sets its parent to inherit the defaults from ONAP Parent
  • Project level external dependencies and versions can be overridden if necessary

All projects participating in simultaneous release will inherit defaults from O-Parent.