| commit | d3168e3c16aa87dce72c540b0a4bd97e914b3fc4 | [log] [tgz] |
|---|---|---|
| author | Michael Dürre <michael.duerre@highstreet-technologies.com> | Mon Jun 13 05:23:15 2022 +0200 |
| committer | Dan Timoney <dtimoney@att.com> | Fri Jul 15 15:38:08 2022 +0000 |
| tree | 2961da32669d06c4c3b2843b637a61393c4f4172 | |
| parent | 2a0882e0d3a8861c7d979515b51101a994239e9b [diff] |
migrate parents to suflur-sr0 adapt odl based parents to suflur-sr0 Issue-ID: CCSDK-3691 Signed-off-by: Michael Dürre <michael.duerre@highstreet-technologies.com> Change-Id: I6fa6ebdb7a43bc4ea63c35650ccd2ff0c253a1dd 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