Details
-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.GA, 7.1.0.DR2
-
None
Description
Some QS which do not include user interface and include Arquillian tests instead, have the wildfly-maven-plugin declared in their pom.xml:
<!-- The WildFly plug-in deploys the WAR to a local JBoss EAP container -->
<!-- To use, run: mvn package wildfly:deploy -->
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>${version.wildfly.maven.plugin}</version>
</plugin>
...
<!-- The WildFly plug-in deploys the WAR to a local JBoss EAP container -->
<!-- To use, run: mvn package wildfly:deploy -->
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
</plugin>
Is this necessary in the pom files where QS are not deployed to server? I would suggest to simplify the pom.xml and include only the necessary stuff. The wildfly maven plugin usage can be found in other QS. What do you think?
One of the examples of affected quickstarts is bean-validation QS.
