commit | ce63934ab223cd83a97a9403bb971e55ac003993 | [log] [tgz] |
---|---|---|
author | Dan Timoney <dtimoney@att.com> | Thu Nov 09 12:28:22 2023 -0500 |
committer | Dan Timoney <dtimoney@att.com> | Thu Nov 09 12:28:22 2023 -0500 |
tree | 8e97b0ff746cebca84eaae4a8beb79e755e58e66 | |
parent | 2c9d634a12406098bd2ea7dbc48f141574187811 [diff] |
Roll master to snapshot version for New Delhi release Roll snapshot version of master to version for next ONAP release Issue-ID: CCSDK-3956 Signed-off-by: Dan Timoney <dtimoney@att.com> Change-Id: Ib15aacb1cfc54a455714f5297154ab5d752d32b8
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