commit | 9af71da2a403c286e1b7a72baa072f243ad54862 | [log] [tgz] |
---|---|---|
author | Dan Timoney <dtimoney@att.com> | Tue Jan 03 15:40:51 2023 -0500 |
committer | Dan Timoney <dtimoney@att.com> | Tue Jan 03 15:40:51 2023 -0500 |
tree | b69573adc468cdc32d3304ac212ccfd56d9803f1 | |
parent | 54f98a18f445d73478e1c3a3a09c70c2d6cea0be [diff] |
Release version 2.5.1 parent poms Release version 2.5.1 parent poms Issue-ID: SDNC-1765 Signed-off-by: Dan Timoney <dtimoney@att.com> Change-Id: I0f724b6a2c597499db241c06571ed8d7fdfb9457
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