Its there to mimic behavior JVZ promised me he would add to Maven but never has (in 3 years). Basically it allows you to *dynamically* alter the test classpath. We don't use it per se because its not really intended for us. Its intended for people running the hibernate testsuite(s) against "other databases".
The build works ok for us without it there, but it needs to be there. On Thu, 2010-01-14 at 14:59 -0300, Hardy Ferentschik wrote: > Speaking of plugins, what does the maven-test-ext-plugin do for us and why > is it needed in > the annotations module? The build seems to work fine even w/o. > > --Hardy > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Steve Ebersole <st...@hibernate.org> Hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
