Hi Gary, I have enabled for CLI project.
Thanks Kanagaraj M *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *************************************************************************************** From: [email protected] [mailto:[email protected]] On Behalf Of Gary Wu Sent: Thursday, July 27, 2017 11:43 PM To: [email protected] Subject: [onap-discuss] [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
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
