Re: [hibernate-dev] No successful builds since move to Maven

2008-05-17 Thread Sanne Grinovero
2008/5/17 Emmanuel Bernard <[EMAIL PROTECTED]>: > OK I found the problem and fixed it as part of the SLF4J migration > It was due to a misconfiguration of ivy.xml in entitymanager and a stale ivy > cache. > You might have to clean your ivy cache rm -fR ~/.ivy/cache > > Emmanuel Hi Emmanuel, thanks

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-17 Thread Emmanuel Bernard
OK I found the problem and fixed it as part of the SLF4J migration It was due to a misconfiguration of ivy.xml in entitymanager and a stale ivy cache. You might have to clean your ivy cache rm -fR ~/.ivy/cache Emmanuel On May 17, 2008, at 08:57, Emmanuel Bernard wrote: On May 17, 2008, a

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-17 Thread Emmanuel Bernard
On May 17, 2008, at 04:29, Sanne Grinovero wrote: 2)The other Hibernate packages (EntityManager, Annotations, Search...) are more tricky: they have a misleading pom there, but you should use the ant build. Unfortunately some links needed by Ivy are currently broken: this is what caused all t

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-17 Thread Sanne Grinovero
Thanks to everybody, you were all very helpful; all your thoughts together made me clarify the situation and I got a partially useful workspace now. (still no search build but now I understand how to proceed) I'll write down what to do if anyone had to repeat this: 1)for Core you have to checkout

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Max Rydahl Andersen
> 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

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Max Rydahl Andersen
>> >> I know you are all quite busy, I can help myself (slowly) but my main >> concern is to understand if these problems are >> A) known, due the fact nobody completed the migration to maven. >> B) You all tested only on IDEA >> C) my environment is completely broken > I only use IntelliJ, so this

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Hardy Ferentschik
On Fri, 16 May 2008 18:51:27 +0200, Sanne Grinovero <[EMAIL PROTECTED]> wrote: Thanks for all the tips, Still I'm unable to build the Hibernate Search project, even using a clean checkout and a fresh maven 2.0.9 repository; using JDK 1.5.0_15-b04. I'm on Linux (LFS), and have installed the so

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Emmanuel Bernard
On May 16, 2008, at 13:51, Sanne Grinovero wrote: 3) EntityManager After having registered annotations, I find out that building entitymanager produces an empty jar registered in my maven repository; no errors, just no compiled classes in the jar. Annotations, EntityManager, Validator, Search

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Chris Bredesen
Steve Ebersole wrote: I even forget the details now. Perhaps I used the command line eclipse generation (mvn eclipse:eclipse) and sent that to Max to test. Do you recall Max? That's the only way I've ever been able to build /trunk in Eclipse. But, the last time was also many moons ago...

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Steve Ebersole
On May 16, 2008, at 11:51 AM, Sanne Grinovero wrote: I know you are all quite busy, I can help myself (slowly) but my main concern is to understand if these problems are A) known, due the fact nobody completed the migration to maven. B) You all tested only on IDEA C) my environment is complete

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Sanne Grinovero
2008/5/16 Max Rydahl Andersen <[EMAIL PROTECTED]>: >> Also before 3.3.0CR1 I could link the projects together instead of making >> jars, so it was easy to navigate the source to make experiments and could >> skip >> all building activities until test phases. > > I could do this the last time too..

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Max Rydahl Andersen
> Also before 3.3.0CR1 I could link the projects together instead of making > jars, so it was easy to navigate the source to make experiments and could skip > all building activities until test phases. I could do this the last time too...but I wondered my self how these things gets done in the mav

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-16 Thread Sanne Grinovero
Thanks for all the tips, Still I'm unable to build the Hibernate Search project, even using a clean checkout and a fresh maven 2.0.9 repository; using JDK 1.5.0_15-b04. I'm on Linux (LFS), and have installed the software mentioned by Steve Ebersole. I don't really need Hibernate Core (although it

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-15 Thread Steve Ebersole
Currently the docbook plugin relies on some system tools for dealing with translations. You would need the GNU GetText toolset and the KDE poxml toolset installed to do full doc builds. Or you could disable docs in the build by using - DdisableDistribution=true That essentially skips the d

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-15 Thread Emmanuel Bernard
This is unfortunate. These glitches were expected, and we will fix them as they pop up. Though as Hardy said, the new HSearch build system is independent of Hibernate Core. All the needed libraries are downloaded in build/lib/ core and build/lib/test IM me if you need more help. AFAIK JBoss

Re: [hibernate-dev] No successful builds since move to Maven

2008-05-15 Thread Hardy Ferentschik
Hi Sanne, I just updated core to the latest and ran 'mvn clean install'. Everything worked fine. Admittedly I had to disable the doc profile in the master pom, because the docbook generation failed, but that's a different issue. I am using maven 2.0.9 and JDK 1.5.0_06. Maybe someone can mak