"scott.stark(a)jboss.org" wrote : | 2. Getting the jbossas build to use maven artifacts. Nothing currently validates the jbossas maven artifacts. The first step in doing this is to replace the legacy jbossbuild repo with the maven repo as the source for the thirdparty contents. How we do this using ivy, maven ant tasks, etc. needs to be defined and documented, and the existing build-thirdparty target replaced. | | The next step would be to replace the existing project dependencies (classpaths defined in tools/etc/buildmagic/modules.ent) with the same type of maven repo references as was done for thirdparty. | | At that point the build and testsuite would be based on the exportable artifacts. | Yes, this is basically my current goal with the mavenization, but I probably should have done a better job of communicating this. I just wanted to point out that ivy or maven ant tasks would be needed only for the testsuite. My plan is to create a new testsuite which is basically a copy of the current one except that the classpath points to the maven generated jars instead of the ant ones. We wouldn't need to modify the existing ant build because once the testsuite works for the maven build, we won't need the existing build anymore. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127987#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...