Difficulty building - fails in Arquillian Container JBoss AS Embedded 6.x

[trungie]

Following instructions on another thread, I downloaded Arquillian 60722a9 from http://github.com/arquillian/arquillian and ran mvn install.

The build fails at Arquillian Container JBoss AS Embedded 6.x

This is my environment:

Apache Maven 3.0-beta-3 (r990787; 2010-08-30 22:44:03+1000)

Java version: 1.6.0_14

Java home: C:\PROGRA~1\Java\jdk1.6.0_14\jre

Default locale: en_AU, platform encoding: Cp1252

OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

{quote}Apache Maven 3.0-beta-3 (r990787; 2010-08-30 22:44:03+1000)
Java version: 1.6.0_14
Java home: C:\PROGRA~1\Java\jdk1.6.0_14\jre
Default locale: en_AU, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"{quote}

I have attached a detailed file running mvn install -rf :arquillian-jbossas-embedded-6 -X.

Any reason it's not working?

Update 1: I have added a sure-fire report for the failing test.

Solved - Update 2: On the advise of another thread, i have downgraded maven to 3.0-beta-2, but now i get another problem - something about the dependency wstx-asl-3.2.1 can not be downloaded?! I read maven was the quickest way to get this up and running!! The new error is here:

{quote}Downloading: http://repository.jboss.org/nexus/content/groups/public/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[WARNING] Unable to get artifact woodstox:wstx-asl:pom:3.2.1 from repository jboss-deprecated (https://repository.jboss.org/nexus/content/repositories/deprecated/): Failure to resolve woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom from https://repository.jboss.org/nexus/content/repositories/deprecated/ was cached in the local repository. Resolution will not be reattempted until the update interval of jboss-deprecated has elapsed or updates are forced. Original error: Error transferring file: Connection timed out: connect
Downloading: http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://repository.jboss.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[WARNING] Unable to get artifact woodstox:wstx-asl:pom:3.2.1 from repository jboss-deprecated (https://repository.jboss.org/nexus/content/repositories/deprecated/): Failure to resolve woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom from https://repository.jboss.org/nexus/content/repositories/deprecated/ was cached in the local repository. Resolution will not be reattempted until the update interval of jboss-deprecated has elapsed or updates are forced. Original error: Error transferring file: Connection timed out: connect
{quote}

[trungie]

I was able to solve the missing dependency problem by putting it in my .m2/repository folder. I have attached it.

It might seem that wstx-asl 3.2.1 is broken. Not sure why according to this external thread.

My bet was that wstx-asl came from maven central and the pom for 3.2.1 did exist at one time but has subsequently been removed for some reason or another (maybe to force people to upgrade), and because everyone has it cached in their local repository already, it all works fine and dandy.

So so painful.

[trungie]

I also had problems with ws-commons:policy:1.0 not being found. I have attached it here. It seems it has been renamed? http://repository.jboss.org/maven2/wscommons-policy/policy/1.0/

So much for being a repeatable build! O_o

[aslak]

They seem to have changed something in Maven 3 Beta3/RC1 that make Embedded AS not work. I've seen some reported issues related to artifact resolution of test scopes, but not found the root cause.

Maven Beta2 seems to be working currently, unless you want to do javadoc generation for api/spi, then Maven 2.2 works..

[jaikiran]

Trung Hoang wrote:

I also had problems with ws-commons:policy:1.0 not being found. I have attached it here. It seems it has been renamed? http://repository.jboss.org/maven2/wscommons-policy/policy/1.0/

FYI - https://jira.jboss.org/browse/JBAS-8422

[trungie]

Disaster, i used Maven 2.2.1 initially and had problems, so on the advise of a thread i upgraded to Maven 3.0.beta-3 then Maven 3.0.beta-2.

I am happy to contribute but i am not familiar with Maven too much. Let me know further details, if you need some hands (even via email).