> I don't understand. Hibernate Search is still using Ant (with Ivy) for the > build. > If you just want to build Hibernate Search you don't even need maven. I > know there > is a POM in the top level directory, but this is not a working maven POM > as such. > The ant to maven mirgration is still a open Jira issue within Hibernate > Search. In fact > I believe it is assigned to me. So far I was waiting for the core > migration to be finished. > Maybe it is a good time to start now ;-) > > Anyways, the ant build works fine. However, I choose > to not depend on 'latest' version defined for commons-annotations, > annotations and entity manager. > I changed ivy.xml to depend on deployed versions from the jboss repo. If > you stick with 'latest' you > WILL have to build these modules locally.
And this is the part i don't understand....does everyone really go around manually calling ant/mvn in the subprojects to get the jar and then be able to build based on latest ? Sound really tedius... /max _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
