commit | 6fa7fc955092595ed2dc4760a569ae178424e4a1 | [log] [tgz] |
---|---|---|
author | Singal, Kapil (ks220y) <ks220y@att.com> | Mon Feb 01 16:11:38 2021 -0500 |
committer | Singal, Kapil (ks220y) <ks220y@att.com> | Mon Feb 01 16:11:38 2021 -0500 |
tree | c47fbe844a1a0399055c1784dac063531a14f6a4 | |
parent | 5700b8593826798ef4f9d0356f852698c1c91bef [diff] |
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
The actual parent poms are being generated from below two pom-template
ccsdk/parent/odlparent/setup/src/main/template/pom-template.xml
ccsdk/parent/springboot/spring-boot-setup/src/main/template/pom-template.xml
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