So based on this morning's call there are two possible plans: a. Paul works on reproducing the current local jbossas trunk thirdparty structure from maven artifacts. This requires that the existing jbossas project artifacts are the same as the current jbossbuild artifacts. The steps to build and test the server would be: a1. Build the jbossas projects that ejb3 depends on using maven to make them available via the maven repo. a2. Build ejb3 to make its artifacts available via the maven repo. a3. Build the remaining jbossas projects using maven to make them available via the maven repo. a4. Run an assembly step equivalent to the current build-thirdparty.xml to produce a local thirdparty repository from the maven repository rather than the jbossbuild repository. This allows the existing build/build-distr.xml, testsuite and eclipse project/classpath settings, config files, etc. to remain unchanged. a5. Run the build/build-distr.xml to create the jboss-5.0.0.CR1 distribution structure. a6. Run the testsuite as ususal to validate the artifacts. Note that this either requires that the target directory for the maven builds use the jbossbuild output/lib convention, or the testsuite module classpaths need to be updated to refer to the target/* locations of the maven build. The B plan would be to simply: b1. Build the jbossas projects that ejb3 depends on using maven to make them available via the maven repo. b2. Build ejb3 to make its artifacts available via the maven repo. b3. Upload the ejb3 artifacts to the jbossbuild repository b4. Run the jbossbuild as ususual. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131570#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...