Hi Jess, Glad to read your message and your support to make this reality.
So basically, we would use the name as they are defined for each repo under "Components Repository name" at https://wiki.onap.org/display/DW/Resources+and+Repositories That sounds like a plan LF can execute on. Thanks, Gildas ONAP Release Manager 1 415 238 6287 -----Original Message----- From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent: Friday, September 08, 2017 10:13 AM To: Gildas Lanilis <gildas.lani...@huawei.com> Cc: onap-discuss@lists.onap.org Subject: [ONAP Helpdesk #45515] Sonar naming convention Dear Gildas, I agree with you that Sonar currently looks all upside down. I was discussing with Andy and Thanh and looks like we might want to make a clean up starting at the root pom.xml which is where this information is pick up from. The root pom.xml should have a parameter called "<name>project</name>" with the repo name as per gerrit and ideally (to keep it consistent) separated by either slash or dashes. Sonar will use this name and artifact parameter to generate the key of each project. Once all pom.xml have been clean up, we can go into Sonar and deal with the leftover projects and do another clean up directly there. Thanh has made this cleanup before for ODL and I would like to help doing this clean up in ONAP. Looking at ODL's Sonar, this is what we should expect to have https://sonar.opendaylight.org/ Please let me know for your comments Thanks a lot! Jess _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
