commit | d06b615678e891f65fda23d52dbff19b3b1ca45e | [log] [tgz] |
---|---|---|
author | Dan Timoney <dtimoney@att.com> | Wed Mar 04 10:58:59 2020 -0500 |
committer | Dan Timoney <dtimoney@att.com> | Wed Mar 04 10:58:59 2020 -0500 |
tree | eaf8e37632035f6812807543f990e94c51524456 | |
parent | 35d607979da73ddb70ec9231491a43b50b1df8e3 [diff] |
Roll to next Frankfurt version Roll to next Frankfurt version Change-Id: I61df38191065778b9bffb4f4a1bd5d17a28b49f4 Issue-ID: CCSDK-2152 Signed-off-by: Dan Timoney <dtimoney@att.com>
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