| commit | 8ca210b4162f01d160171607cf27d6fe059db73e | [log] [tgz] |
|---|---|---|
| author | Dan Timoney <dtimoney@att.com> | Mon Apr 27 14:58:54 2020 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Mon Apr 27 14:58:54 2020 +0000 |
| tree | 1035368679489d2b1529410ba5bc19a05ccb6df9 | |
| parent | 7047ebfdadbaff197bb1aa976cd1b331cd77e614 [diff] | |
| parent | 0fa4ccfa20b2a4971b5d1d34339ae9191060eba9 [diff] |
Merge "Roll to next snapshot version" into frankfurt
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