gCubeSystem
/
maven-parent
15
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove property on gcube-developer activation.

This commit is contained in:
Manuele Simi 2019-05-18 15:19:22 -04:00
parent a8ef41d122
commit afbb7af994
1 changed files with 1 additions and 52 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
pom.xml
View File

@ -56,10 +56,8 @@
<profile>
<id>gcube-developer</id>
<activation>
<!-- This profile will automatically be active for all builds unless another profile in the POM is activated -->
<activeByDefault>true</activeByDefault>
<property>
<name>!jenkins-releases</name>
</property>
</activation>
<!-- Repositories for dependency resolution -->
@ -152,40 +150,12 @@
</profiles>
<build>
<pluginManagement>
<plugins>
<!--
maven-assembly-plugin configuration
Defines some default assemblies. The configuration is not bound to any phase, so they are not created
by default. To use them, a component must bound them to a phase.
E.g.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>make-uberjar</id>
<phase>install</phase>
</execution>
<execution>
<id>make-servicearchive</id>
<phase>install</phase>
</execution>
</executions>
</plugin>
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.6</version>
@ -197,27 +167,6 @@
</dependency>
</dependencies>
<executions>
<!-- Disable the execution of the legacy servicearchive. When/If a centralized
generation of binary packages is implemented, this will allow to disable the
execution of the plugin specified in the single pom files -->
<!--
<execution>
<id>servicearchive</id>
<configuration>
<skipAssembly>true</skipAssembly>
</configuration>
<phase>install</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
-->
<!-- uberjar creation -->
<execution>
<id>make-uberjar</id>