| commit | 67cb8d57527df08bd6997eb8b500ce31139016ce | [log] [tgz] |
|---|---|---|
| author | Michael DÜrre <michael.duerre@highstreet-technologies.com> | Mon Apr 12 13:11:00 2021 +0200 |
| committer | Michael DÜrre <michael.duerre@highstreet-technologies.com> | Thu May 27 07:17:00 2021 +0200 |
| tree | e9b4afc30bf56039d7a90a2f53682d3eac8f385e | |
| parent | 9714cfc592c9ca285bc0c70b659c024289690e6c [diff] |
migrate parents to silicon actually silicon-SR0 but later for SR1 Issue-ID: CCSDK-3267 Signed-off-by: Michael DÜrre <michael.duerre@highstreet-technologies.com> Change-Id: I066e204dc9dc674c6c40e72fe7561dbdbc9cbe6a Signed-off-by: Michael DÜrre <michael.duerre@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