| commit | 54f98a18f445d73478e1c3a3a09c70c2d6cea0be | [log] [tgz] |
|---|---|---|
| author | highstreetherbert <herbert.eiselt@highstreet-technologies.com> | Thu Dec 08 16:51:41 2022 +0100 |
| committer | highstreetherbert <herbert.eiselt@highstreet-technologies.com> | Thu Dec 08 16:52:02 2022 +0100 |
| tree | 8828af739eb442160a1d4de865fefcd63e7e90b0 | |
| parent | d04c3e4e36827cfe52fef52231b28f27264ab380 [diff] |
SDNC not starting with SDNR features Issue-ID: SDNC-1765 Signed-off-by: highstreetherbert <herbert.eiselt@highstreet-technologies.com> Change-Id: I32ae2b500fb3db86da419feaa06e78995a88b43a Signed-off-by: highstreetherbert <herbert.eiselt@highstreet-technologies.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