I edited the settings.xml in<jboss_as_trunk>\tools\maven\conf and executed build, the build succeeded.

In my local ~/.m2/repository directory are the following files:

D:\.m2\repository\org\jboss\jbossas\jboss-as-hornetq-int\6.1.0-SNAPSHOT\jboss-as-hornetq-int-6.1.0-SNAPSHOT.jar

D:\.m2\repository\org\jboss\jbossas\jboss-as-hornetq-int\6.1.0-SNAPSHOT\jboss-as-hornetq-int-6.1.0-SNAPSHOT.pom

D:\.m2\repository\org\jboss\jbossas\jboss-as-hornetq-int\6.1.0-SNAPSHOT\jboss-as-hornetq-int-6.1.0-SNAPSHOT-sources.jar

D:\.m2\repository\org\jboss\jbossas\jboss-as-hornetq-int\6.1.0-SNAPSHOT\maven-metadata-local.xml

D:\.m2\repository\org\jboss\jbossas\jboss-as-hornetq-int\6.1.0-SNAPSHOT\_maven.repositories

When I started the build in <jboss_as_trunk>\testsuite I get the message:

BUILD FAILED

D:\jboss_svn\jboss_as_trunk\testsuite\build.xml:690: Unable to resolve artifact: Missing:

----------

1) org.jboss.jbossas:jboss-as-hornetq-int:jar:6.1.0-SNAPSHOT

  Try downloading the file manually from the project website.

   Then, install it using the command:

      mvn install:install-file -DgroupId=org.jboss.jbossas -DartifactId=jboss-as-hornetq-int -Dversion=6.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:

      mvn deploy:deploy-file -DgroupId=org.jboss.jbossas -DartifactId=jboss-as-hornetq-int -Dversion=6.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:

        1) org.jboss.jbossas:jboss-as-testsuite:pom:6.1.0-SNAPSHOT

        2) org.jboss.jbossas:jboss-as-hornetq-int:jar:6.1.0-SNAPSHOT

2) org.jboss.jbossas:jboss-as-depchain:pom:6.1.0-SNAPSHOT

  Path to dependency:

        1) org.jboss.jbossas:jboss-as-testsuite:pom:6.1.0-SNAPSHOT

        2) org.jboss.jbossas:jboss-as-depchain:pom:6.1.0-SNAPSHOT

----------

2 required artifacts are missing.

for artifact:

  org.jboss.jbossas:jboss-as-testsuite:pom:6.1.0-SNAPSHOT

from the specified remote repositories:

  central (http://repo1.maven.org/maven2),

  jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/),

  jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/)

Why does is try to get the file from the remote repositories?

Is there a work around?

Thanks!

I found something: in build.xml of testsuite there is the following line....

<property name="maven.repo.local" location="${user.home}/.m2/repository"/>

So my jars in D:\.m2\repository could not be found,

I use now the default settings (${user.home}/.m2/repository") and try both builds again.

You are right, so wouldn't it be a good idea to mention it in the manual (the readme.txt in http://anonsvn.jboss.org/repos/jbossas/trunk)?

One could introduce a MAVEN_REPO_HOME which points to the local maven repository and is referred all build.xmls?

The build of testsuite now also was successful. ;-) I 'm going on!!!

It's me again....;-)

I imported the maven project into eclipse by selecting the root dir of the jboss_as_trunk, where the pom.xml resides.

After that I defined a JBoss Server 6 runtime (poiting to  <jboss_as_trunk>\build\target\jboss-6.1.0-SNAPSHOT,

but the server could not start.

"C:\Program Files\Java\jdk1.6.0_24\bin\javaw.exe" -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:63202 "-Dprogram.name=JBossTools: JBoss 6.0 Runtime" -Xms256m -Xmx768m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=D:\jboss_svn\jboss_as_trunk\build\target\jboss-6.1.0-SNAPSHOT\lib\endorsed -Djava.library.path=D:\jboss_svn\jboss_as_trunk\build\target\jboss-6.1.0-SNAPSHOT\bin\native; -Dfile.encoding=Cp1252 -classpath D:\jboss_svn\jboss_as_trunk\build\target\jboss-6.1.0-SNAPSHOT\bin\run.jar org.jboss.Main --configuration=default -b localhost -Djboss.server.base.url=file:/D:/jboss_svn/jboss_as_trunk/build/target/jboss-6.1.0-SNAPSHOT/server/

I got a StackOverflowError.

And another error: I strated "build tests" in dir testsuite, the error is:

tests-standard-unit:

     [echo]

     [echo]    junit.timeout:              300000

     [echo]    jbosstest.iterationcount:   10

     [echo]    jbosstest.threadcount:      5

     [echo]    jbosstest.beancount:        5

     [echo]

    [junit] Running org.jboss.test.aop.test.AOPUnitTestCase

    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec

BUILD FAILED

D:\jboss_svn\jboss_as_trunk\testsuite\build.xml:1310: The following error occurred while executing this line:

D:\jboss_svn\jboss_as_trunk\testsuite\build.xml:1375: The following error occurred while executing this line:

D:\jboss_svn\jboss_as_trunk\testsuite\build.xml:1806: Process fork failed.

Total time: 1 minute 2 seconds

Testsuite shutdown hook found server "all" still running; stopping it.

Shutting down server: all

log4j:WARN No appenders could be found for logger (org.jnp.interfaces.TimedSocketFactory).

log4j:WARN Please initialize the log4j system properly.

shutdownTimeout will be=45

Server stopped.

It's an adventure, 1 day for 1 step!!!!