-
1. JBPAPP build failure
eabrand Mar 17, 2011 10:32 AM (in response to sewatech)Did you figure out the reason for this error? I'm getting the same one.
Thanks!
-
2. JBPAPP build failure
sewatech Mar 17, 2011 11:10 AM (in response to eabrand)Hi Emily,
Unfortunately, I have no solution. In fact, I gave away.
The good news is that the build process has been enhanced and is much simpler in JBoss AS 6 and 7.
If you find the solution, I'd apreciate to hear about it.
-
3. JBPAPP build failure
eabrand Mar 17, 2011 11:14 AM (in response to sewatech)The ant build script in the build folder works beautifully. I think the first problem is that we should've been doing mvn clean install in the build directory not the jboss-as directory.
However, when I do run the maven script in the build directory I get the following errors:
----------
12 required artifacts are missing.
for artifact:
org.jboss.jbossas:jboss-as-build:pom:5.1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
prod-repository.jboss.org (http://repository.jboss.org/maven2-brew),
repository.jboss.org (http://repository.jboss.org/maven2),
snapshots.jboss.org (http://snapshots.jboss.org/maven2)
When I looked to see if it was my internet connection the artifacts are actually missing from those repositories so I'm not sure if maven works at all as a build script for JBoss EAP 5.0.1
-
4. JBPAPP build failure
sewatech Mar 18, 2011 3:08 AM (in response to eabrand)You're probably right. Maven pom.xml files seem to be here as par of the Ant build, not for pure maven builds.
-
5. JBPAPP build failure
eabrand Mar 18, 2011 7:21 PM (in response to sewatech)I did find the solution to the problem though. The version in the pom.xml file should be 5.1.0.GA not 5.1.0-SNAPSHOT. If you change that version in all of the poms you will be able to run maven without a problem. I also added the following to the pom.xml in the jboss-as directory just in case:
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>jboss-deprecated</id>
<name>JBoss Deprecated</name>
<url>https://repository.jboss.org/nexus/content/repositories/deprecated</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>jboss-nexus-repository</id>
<name>JBoss Nexus Repository</name>
<url>https://repository.jboss.org/nexus</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
-
6. JBPAPP build failure
sewatech Mar 19, 2011 5:58 PM (in response to eabrand)Unfortunatly, it does not work for me. Where do you launch your "mvn install" from ?
When I launch it from the build directory, it does not find org.jboss.system:system-jmx:jar:5.1.0.GA and fron root directory, maven complains about some missing versions on some dependencies.
-
7. JBPAPP build failure
eabrand Mar 20, 2011 12:09 PM (in response to sewatech)I only tested it in the jboss-as/jbossas directory. You might need to do mvn clean install in each module instead of in the entire jboss-as directory. Let me know how that goes.
-
8. JBPAPP build failure
eabrand Mar 22, 2011 1:01 PM (in response to eabrand)I found the underlying error:
Open <SOURCE FOLDER HOME>/jboss-as/system-jmx/pom.xml. Add the following into the <dependencies>...</dependencies>
<dependency>
<groupId>org.jboss.cl</groupId>
<artifactId>jboss-classloader</artifactId>
</dependency>
Open <SOURCE FOLDER HOME>/jboss-as/ejb3/pom.xml. Add the following into the <dependencies>...</dependencies>
<dependency>
<groupId>org.jboss.ejb3</groupId>
<artifactId>jboss-ejb3-endpoint-deployer</artifactId>
</dependency>
Also change 5.1.0-SNAPSHOT in <version> tags of all of the poms (jboss-as and sub-folders) to 5.1.0.GA