Removing need for boilerplate app.xml; Instead defining onos.app.name and onos.app.origin (optional) is sufficient to trigger generation of boilerplate app.xml and features.xml files.
Change-Id: If50cc3a18134602d47fcf6f240ee6b0a20c6c329
diff --git a/database-perf/pom.xml b/database-perf/pom.xml
index 3a39614..b40f6d5 100644
--- a/database-perf/pom.xml
+++ b/database-perf/pom.xml
@@ -31,24 +31,8 @@
<description>Partitioned database performance test application</description>
- <build>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-assembly-plugin</artifactId>
- <version>2.5.3</version>
- <configuration>
- <descriptor>src/assembly/bin.xml</descriptor>
- </configuration>
- <executions>
- <execution>
- <phase>package</phase>
- <goals>
- <goal>single</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
+ <properties>
+ <onos.app.name>org.onosproject.dbperf</onos.app.name>
+ </properties>
+
</project>