test: configure test project to not run twice

Some tests had been configured in a way that they had both the extension
as well as an explicit call to the plugin. Which resulted the plugin
running twice, one time with the default configuration. Another time
with the explicit configuration.

This results in the RPM file being created twice. But in the case of the
"forcerelease" test, with too different output file names.

This change configures the test project correctly, so that there is no
explicit invocation of the plugin, only the configuration of the
implicit step, triggered by enabling the plugin as an extension.

closes ctron#63

src/it/test14-forcerelease/pom.xml

@@ -43,29 +43,21 @@
 				<artifactId>rpm</artifactId>
 				<extensions>true</extensions>
 				<version>@project.version@</version>
-				<executions>
-					<execution>
-						<goals>
-							<goal>rpm</goal>
-						</goals>
-						<configuration>
-							<group>Application/Misc</group>
+				<configuration>
+					<group>Application/Misc</group>
 
-							<forceRelease>true</forceRelease>
-							<snapshotVersion>1.2.3</snapshotVersion>
-							<version>4.5.6</version>
+					<forceRelease>true</forceRelease>
+					<snapshotVersion>1.2.3</snapshotVersion>
+					<version>4.5.6</version>
 
-							<signature>
-								<keyId>${keyId}</keyId>
-								<keyringFile>${user.home}/.gnupg/secring.gpg</keyringFile>
-								<passphrase>${passphrase}</passphrase>
-								<hashAlgorithm>SHA1</hashAlgorithm>
-								<skip>${skipSigning}</skip>
-							</signature>
-
-						</configuration>
-					</execution>
-				</executions>
+					<signature>
+						<keyId>${keyId}</keyId>
+						<keyringFile>${user.home}/.gnupg/secring.gpg</keyringFile>
+						<passphrase>${passphrase}</passphrase>
+						<hashAlgorithm>SHA1</hashAlgorithm>
+						<skip>${skipSigning}</skip>
+					</signature>
+				</configuration>
 			</plugin>
 		</plugins>
 	</build>