Adding deployeAtEnd true to maven-deploy-plugin

It will avoid scenario where few child modules have artifacts created in nexus and some are missing

Issue-ID: CCSDK-3126
Signed-off-by: Singal, Kapil (ks220y) <ks220y@att.com>
Change-Id: I153719d9125213dc20b646d3fdfb31c8546ad49f
12 files changed
tree: c47fbe844a1a0399055c1784dac063531a14f6a4
  1. dependencies-bom/
  2. dependencies-odl-bom/
  3. docs/
  4. installed-odl-bom/
  5. odlparent/
  6. oparent/
  7. releases/
  8. springboot/
  9. standalone/
  10. tools/
  11. .gitignore
  12. INFO.yaml
  13. pom.xml
  14. Readme.MD
  15. version.properties
Readme.MD

!!!!! PLEASE READ !!!!!

The actual parent poms are being generated from below two pom-template

ODL related parent poms:

ccsdk/parent/odlparent/setup/src/main/template/pom-template.xml

Springboot related parent poms:

ccsdk/parent/springboot/spring-boot-setup/src/main/template/pom-template.xml

Note:

Any updates needed should be made to respective template and not to the generated pom.xml file/files.

Every parent pom has associated properties files (src/main/properties).
Setup module will read those properties and populate respective values within generated pom.xml