Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oparent / dc0d02e1e6cb53b13c06373da32d36dd9230f392
commitdc0d02e1e6cb53b13c06373da32d36dd9230f392[log] [tgz]
authorDan Timoney <dtimoney@att.com>Fri Sep 01 13:45:40 2017 -0400
committerDan Timoney <dtimoney@att.com>Fri Sep 01 17:44:53 2017 -0400
treec646818e4ac84aada8f0d3642122499170024e8b
parent553868f6b9898ae1cdd2f4cbb566e5d33b7f1af4 [diff]
Add parent for opendaylight vclients

Applications based on opendaylight need to inherit settings from the
opendaylight parent pom (odlparent).  This change adds a copy of
oparent whose parent is the odlparent pom, which will allow projects
based on opendaylight to still inherit settings from oparent.
The new odlparent-boron directory is included as module in top
level pom.xml, per review comments, to avoid release build failure.
This will have to be treated via a separate Jenkins build.

Change-Id: Icfb1f119672efc7cfd80748ee92cc331b01550a5
Issue-ID: CCSDK-43
Signed-off-by: Dan Timoney <dtimoney@att.com>
1 file changed
tree: c646818e4ac84aada8f0d3642122499170024e8b
  1. checkstyle/
  2. license/
  3. oparent/
  4. oparent-odlparent/
  5. version-check-maven-plugin/
  6. .gitattributes
  7. .gitignore
  8. .gitreview
  9. LICENSE.txt
  10. pom.xml
  11. README.md
  12. settings.xml
  13. 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.