jboss-as-maven-plugin Deployment fails

[bmaurer]

Hi,

I am porting our project from an ant-build to a maven-build. I used the jboss-javaee6-ear-webapp Archetype as a base.

So my setup also consists of a super-pom, an ear, ejb and war sub-module. I have also copied the jboss-as-maven-plugin config

(and tried it with 3 different versions of the plugin).

But the deployment still fails with:

[INFO] Reactor Summary:

[INFO]

[INFO] myProg Framework ................................... SUCCESS [  0.390 s]

[INFO] myProgEJB module .................................. SUCCESS [  3.848 s]

[INFO] myProgWeb module .................................. FAILURE [  0.051 s]

[INFO] myProgEAR module .................................. SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 4.711 s

[INFO] Finished at: 2015-12-11T13:49:48+01:00

[INFO] Final Memory: 49M/520M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal on project myProg-web: Could not resolve dependencies for project at.mycomp:myProg-web:war:1.0-SNAPSHOT: Could not find artifact at.mycomp:myProg-ejb:jar:1.0-SNAPSHOT -> [Help 1]

mvn compile and mvn package work just fine and I can copy the EAR manually to my jboss deployment folder.

In the super-pom:

			<plugin>
				<groupId>org.jboss.as.plugins</groupId>
				<artifactId>jboss-as-maven-plugin</artifactId>
				<version>7.7.Final</version>
				<inherited>true</inherited>
				<configuration>
					<skip>true</skip>
				</configuration>
			</plugin>

In the ear-pom:

		<plugin>
			<groupId>org.jboss.as.plugins</groupId>
			<artifactId>jboss-as-maven-plugin</artifactId>
			<configuration>
				<skip>false</skip>
				<port>9993</port>
			</configuration>
		</plugin>

[jamezp]

This looks like an issue with your general configuration instead of an issue with the jboss-as-maven-plugin. I assume you'd see the same issue if you did mvn clean package.

You need to add a dependency to your myProgWeb to the myProgEJB.

--

James R. Perkins

[bmaurer]

Ups, there is a typo in my original post under the error message. I meant "mvn package" not "mvn deploy".

"mvn clean package" works like a charm and as I said in my original post, if I copy the ear manually that

works (at least deployment starts, it does fail later on, but that's a different issue