| commit | e816a5916736d263227f5a800561ead9ad81ce27 | [log] [tgz] |
|---|---|---|
| author | Dan Timoney <dtimoney@att.com> | Thu Sep 03 08:56:01 2020 -0400 |
| committer | Dan Timoney <dtimoney@att.com> | Thu Sep 03 08:56:04 2020 -0400 |
| tree | 56c942b219c85e52a7cad276efd3a0717e6e6e93 | |
| parent | 3716136cdf88bef2fc15b821f83e139f6bd2ce05 [diff] |
Address javadoc build issues maven-javadoc-plugin started to fail when using java 11 compiler. Some issues are addressed in latest version of plugin (3.2.0), but it appears some issues remain. To address this, we use the latest plugin version and configure maven to continue if javadoc errors occur. Note: this issue is currently causing verify builds to fail - thus, this is a blocking issue. Change-Id: I0a9882b4b93ea18b29e2d53d269cf70dda77a4d1 Issue-ID: CCSDK-2728 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