| commit | b6288f99fbfcc73f115511696f98111ca32b8d2f | [log] [tgz] |
|---|---|---|
| author | Michael DÜrre <michael.duerre@highstreet-technologies.com> | Tue Dec 01 13:34:56 2020 +0100 |
| committer | Dan Timoney <dtimoney@att.com> | Wed Jan 27 18:50:58 2021 +0000 |
| tree | 9ce2959d1e30416e1bb27440c67be5a6e1a7a08c | |
| parent | b56e7814288411c208664aceaa60c110ff09d115 [diff] |
ccsdk parents for alu-sr0 migrate parents to aluminium-sr0 Issue-ID: CCSDK-3012 Signed-off-by: Michael DÜrre <michael.duerre@highstreet-technologies.com> Change-Id: I8c19abcfa4a0fbac629496835e4caf92aecd2459 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