"pgier" wrote : 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.
Let's guinea pig EJB 3 for this. We can use the ejb3-core test suite as a blue print
for how AS test suite is going to work. It has all aspects in there (starting/stopping
instances of JBoss, doing deployment and unit tests etc).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127998#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...