Hi Catherine,
In today's Integration meeting, we discussed having CLAMP pilot trials around
coding styles. In OPEN-O we centrally defined coding styles in the oparent
project/repo, and it would be great if we can do likewise for ONAP so we can
avoid duplicate or conflicting definitions across projects. Do you think we
can have CLAMP do a pilot run on inheriting from oparent as well?
To recap the goals of oparent: centrally define shared parent POM definitions
such as nexus (distributionManagement) location, coding styles, license checks,
coding style checks, sonar setup, etc.
To inherit from oparent: modify the project's POM to ensure that all POM files
ultimately inherit from
<parent>
<groupId>org.onap.oparent</groupId>
<artifactId>oparent</artifactId>
<version>1.0.0-SNAPSHOT</version>
</parent>
And also remove any local definitions within the project POMs around
distributionManagement, coding styles, etc., so that those properties are
derived from oparent instead.
Please let us know if you run into anything that would require changes or
enhancements to the oparent POMs.
Thanks,
Gary
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
