commit | 7e70156de2c31e2fc8e90a8f22905e7febba5af7 | [log] [tgz] |
---|---|---|
author | Michael Dürre <michael.duerre@highstreet-technologies.com> | Tue Jul 26 08:21:50 2022 +0200 |
committer | Michael Dürre <michael.duerre@highstreet-technologies.com> | Tue Jul 26 08:22:23 2022 +0200 |
tree | 67eded8d38b96520e18593d079f877b97ec2f453 | |
parent | 59d34e4b2c6e1851b51412b5291425c1564f733c [diff] |
fix dmaap dependent odl startup issue fix version for dmaap client for odl bundles Issue-ID: CCSDK-3731 Change-Id: I212b3d679cf059f292b5ed98b0584fa259408732 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