-
Bug
-
Resolution: Done
-
Major
-
7.0.0.GA
-
None
All the quickstart parent projects have version.wildfly.maven.plugin property with the definition of version of WildFly Maven plugin to use. Some of the multi-module quickstarts use WildFly Maven plugin in their child modules, but the version of the plugin is not defined:
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<configuration>
<skip>false</skip>
<filename>${project.build.finalName}.jar</filename>
</configuration>
</plugin>
This may (eventually) let some unexpected behaviour to arise.
Suggested fix:
Add a line with version property to child module POMs.
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>${version.wildfly.maven.plugin}</version>
<configuration>
<skip>false</skip>
<filename>${project.build.finalName}.jar</filename>
</configuration>
</plugin>
Affected files:
- cluster-ha-singleton/service/pom.xml
- ejb-throws-exception/ear/pom.xml
- jts/application-component-1/pom.xml
- jts/application-component-2/pom.xml
- kitchensink-ear/ear/pom.xml
- kitchenisnk-ml-ear/ear/pom.xml
- shopping-cart/server/pom.xml
- is related to
-
-
- Verified
-
