IMO the best approach is a separate module for the test helper/infrastructure bits. This is what we do in core with the hibernate-test module as opposed to the hibernate-testsuite module.
To me it makes the intent clearer. If I see including a testuite (test-jar artifact) I immediately think inclusion of those tests for running. On 03/14/2010 02:51 PM, Sanne Grinovero wrote: > Hello, > while writing tests for Infinispan I would like to be able to depend > on Hibernate Search's testsuite, as it contains several helpers which > I would use. > This happened me on other projects too, quite always if Lucene is involved. > > Would you be ok in publishing the maven artifacts of the testsuite too? > Infinispan is doing that for core, and it's nice to have general > testing utilities available on the test classpath of other modules; > It's probably going to be required anyway wen modularizing Hibernate Search. > > I have the local changes ready, just need an ok for commit; it only > implies some additional entries for the configuration of > maven-jar-plugin. > > Cheers, > Sanne > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- st...@hibernate.org http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
