Remove oParent and sonar.java.binaries.
This is to fix Sonar code coverage reporting.
Issue-Id: PORTAL-50
Change-Id: Ib222f60587405924653d201a7f5f057d018e8bf5
Signed-off-by: Manoop Talasila <talasila@research.att.com>
diff --git a/pom.xml b/pom.xml
index a4734a3..3f46cef 100644
--- a/pom.xml
+++ b/pom.xml
@@ -3,12 +3,12 @@
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
- <parent>
+ <!--<parent>
<groupId>org.onap.oparent</groupId>
<artifactId>oparent</artifactId>
<version>0.1.1</version>
<relativePath />
- </parent>
+ </parent>-->
<groupId>org.onap.portal</groupId>
<artifactId>onap-portal-parent</artifactId>
@@ -46,7 +46,7 @@
<sonar.projectBaseDir>${project.basedir}</sonar.projectBaseDir>
<sonar.exclusions>**/scripts/**/*,**.js</sonar.exclusions>
<sonar.test.exclusions>**/test/**/*,**/tests/**/*</sonar.test.exclusions>
- <sonar.java.binaries>.</sonar.java.binaries>
+ <!--<sonar.java.binaries>.</sonar.java.binaries>-->
</properties>
<!-- Specify the repositories here to avoid coordination of ~/.m2/settings.xml