"pgier" wrote : | 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. | The problem is I don't know that we can wait for mavenization of jbossas for CR1. We can't have an unusable trunk for any amount of time (other than next week) as there is too much work to do. We also can't have the tck runs impacted. So what I'm suggesting is that start using the maven repo with the current ant build to validate artifacts, classpaths, eclipse project files, etc. Once that is working, how everything is mavenized can be decided. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128003#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...