Just giving everyone the heads up that I an planning to do the Search build refactoring, starting probably later today or latest tomorrow.
I don't think that it will be hard to merge any outstanding changes you have into the new layout, but in case you think you need more time to check something in let me know. --Hardy On Mon, 15 Mar 2010 07:49:27 -0300, Sanne Grinovero <sanne.grinov...@gmail.com> wrote: > 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. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
