Browse Source

Build: Remove profile to create attached RPM

This is no longer necessary, as the RPM is now built as
a primary artifact, so no need to deploy it as a secondary
artifact anymore.

Closes #12529
Alexander Reelsen 10 years ago
parent
commit
c423319dda
1 changed files with 0 additions and 25 deletions
  1. 0 25
      distribution/rpm/pom.xml

+ 0 - 25
distribution/rpm/pom.xml

@@ -338,31 +338,6 @@
     </build>
 
     <profiles>
-        <profile>
-            <id>release</id>
-            <activation>
-                <property>
-                    <name>package.rpm</name>
-                    <value>true</value>
-                </property>
-            </activation>
-            <build>
-                <plugins>
-                    <plugin>
-                        <groupId>org.codehaus.mojo</groupId>
-                        <artifactId>rpm-maven-plugin</artifactId>
-                        <executions>
-                            <execution>
-                                <id>attach-rpm</id>
-                                <goals>
-                                    <goal>attached-rpm</goal>
-                                </goals>
-                            </execution>
-                        </executions>
-                    </plugin>
-                </plugins>
-            </build>
-        </profile>
         <profile>
             <id>sign-rpm</id>
             <activation>