you're right, but how should I "mark these as non stable APIs" ? These artifacts are not included in the main jar, so if somebody wants to depend on them they are supposed to know what they're doing.
I've created HSEARCH-467 and the pom change is committed - I'll keep it open to apply some warning you might want to add somewhere. We can write something in the Manifest, but that's not likely to be read, WDYT? Sanne 2010/3/15 Emmanuel Bernard <emman...@hibernate.org>: > My problem with that is that we don't spend as much energy as we do for the > core product on API stability. We should clearly mark these as non stable > APIs. > Aside from that, feel free to go. Maybe we should split the helper bits in a > dedicated submodule once we have a multi module Hibernate Search. > > On 14 mars 2010, at 20:51, 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 > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
