Oops, sorry, please disregard; this was sent to the wrong email list. Thanks, Gary
_____________________________________________ From: Gary Wu Sent: Thursday, July 27, 2017 11:09 AM To: [email protected] Subject: [integration] Update POM to inherit from oparent Hello PTLs, O-Parent (repo: oparent) is a parent POM that centrally defines shared configuration items such as Nexus (distributionManagement) location, license checks, coding style checks, sonar setup, etc. https://wiki.onap.org/pages/viewpage.action?pageId=10783020. The ultimate goal is ensure consistency across ONAP projects, and free individual projects from redundant work whenever the standard configurations need to be changed. To make this work, we request the following help from each project: 1. Modify POMs to inherit from oparent, 2. Remove applicable local configuration properties in individual POM files 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> If your seed code came from OPEN-O, note that the groupId has been changed to org.onap instead of org.openo. Once the above is done, please 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 the Integration team know if you run into anything that would require changes or enhancements to the oparent POMs. Thanks, Gary
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
