thanks for the help. Unfortunately, the pom.xml of my sample now looks the same as yours, including the repositories. But before reaching this state, I had used some other repositories (found e.g. in the Arquillian docs). Might it happen that Maven "caches" data from an invalid repository? Any chance to force a refresh of this (besides deleting the complete maven cache)?

I will give my project another try this evening and hope that after a day of idle time, Maven will refresh itself...

To sum up the problems from my last two posts:

a) the page http://www.jboss.org/jsfunit/building-jsfunit.html seems to contain the instructions for JSFUnit 1.3, am I right? E.g. for JBoss 6, the "-P" value seems to be ""mvn.bat -Pjbossas-remote-6". Could you add also the JSFUnit2 profiles? And what is the full maven call to build JSFUnit2 against a remote JBoss 6 with Mojarra 2.0?

b) When using "mvn.bat -Pjbossas-remote-6 ...", the sample at "jsfunit-2.0.0.Snapshot\examples-arquillian\hellojsf" does not compile (see above) You fixed a similar issue in the "gettingstarted" sample - where the repo was wrong.

a) the page http://www.jboss.org/jsfunit/building-jsfunit.html seems to contain the instructions for JSFUnit 1.3, am I right? E.g. for JBoss 6, the "-P" value seems to be ""mvn.bat -Pjbossas-remote-6". Could you add also the JSFUnit2 profiles? And what is the full maven call to build JSFUnit2 against a remote JBoss 6 with Mojarra 2.0?

The -P values are still valid for everything except the modules that use Arquillian. Those are under /examples-arquillian and /gettingstarted. To run those tests under remote JBoss 6, you would:

start an instance of JBoss AS6

mvn -Pjbossas-remote-6 test

Note that in the above case, "test" is the Maven goal where in the Cactus-based tests I have a profile named "test".

Wolfgang Knauf wrote:

b) When using "mvn.bat -Pjbossas-remote-6 ...", the sample at "jsfunit-2.0.0.Snapshot\examples-arquillian\hellojsf" does not compile (see above) You fixed a similar issue in the "gettingstarted" sample - where the repo was wrong.

well, the "JBoss switches off an old repository" really causes trouble... I killed my old ".m2\repository" directory, and now I receive those errros when trying to build the "gettingstarted" sample (command line: "mvn.bat test -Pjbossas-remote-6"):

Hope I don't have to kill my complete repository - my internet is poorly slow - this would be one hour of downloading again :-(.

When Maven builds a project and encounters a dependency, it first checks your local repo (on your filesystem) for that specific, {groupid, artifactid, version, type} combination. If it finds that artifact in your local repo, then it will not go looking for the artifact in the remote repo (the one hosted by jboss.org or Maven central). So artifacts which are already downloaded won't be downloaded again, even if the remote repo is deleted or moved, unless ofcourse you force maven to do so by cleaning your local repo.

I figured out where your Trove dependency is coming from. Since you are running with jbossas-remote-6, you are using the jboss-as-client, which pulls in everything but the kitchen sink.

Give this a try for gettingstarted:

mvn clean

mvn -Pjetty-embedded test

I see something else that's strange about Trove. Your output is looking for Trove 2.1.1, which is the incorrect version (see link). When I ask for the dependencies, I get the correct version, which is 1.0.2.

If you want to see the full dependency graph, do this from the gettingstarted directory: