| commit | e0bd7ca9e68e1789671cb2e201f409a2aef8e544 | [log] [tgz] |
|---|---|---|
| author | Dan Timoney <dtimoney@att.com> | Thu Apr 09 14:46:31 2020 -0400 |
| committer | Dan Timoney <dtimoney@att.com> | Thu Apr 09 18:48:11 2020 +0000 |
| tree | bf74f034ba5f454cbbe36fe86710f5d71d5a4480 | |
| parent | 232b36b34ed82c76d6dafe2defd354cfb08a8637 [diff] |
Updated script to handle sed issues
The 'sed' line added to the updParentVersion script introduced 2 problems:
1) sed inline edit (-i option) saves a backup copy unless you pass the
empty string ('') as the suffix , which is the arg to the -i option.
2) BSD sed (e.g. the version installed in Mac OSX) does not support \n
as newline in replacement strings. The more portable solution is to
simply escape a literal newline in the replacement string.
Change-Id: Ia3a3b2635b8cc9ce57ec41c2e55c1384587325c7
Issue-ID: CCSDK-2308
Signed-off-by: Dan Timoney <dtimoney@att.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