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 was really useful to have all projects configured and linked in eclipse as dependencies), but I need to build it as the latest Search trunk depends on latest Core tag; I want to avoid the "please send me a built jar" approach. I am collecting some of the problems I found: 1)To create an eclipse project for Core, I had to disable the m2eclipse maven plugin, manually select all source directories, download all jar dependencies and force source level to 1.5. 2)Annotations Even when producing the Core distfiles using maven from command line, not all dependent projects find it in the repository, I had to re-register the jar using: mvn install:install-file -DgroupId=org.hibernate -DartifactId=hibernate -Dversion=3.3.0.CR1 -Dpackaging=jar -Dfile= I don't really understood the problem, is it possible that different projects give a different name to it? 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. 4)Search Even when skipping or manually resolving the other issues, to build Search there is a dependency on lucene 2.3.1 but the URL appears to be wrong; I don't know how it finds the url, but he is downloading http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lucene-core-2.3.1.pom (the signature) instead of http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lucene-core-2.3.1.pom.xml And the same problem for "lucene-parent". 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 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 regarding option C, I deleted my workspace and all maven repository, fresh checkout and repeated all tests.. no luck. regards, Sanne 2008/5/16 Steve Ebersole <[EMAIL PROTECTED]>: > 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 documentation and distribution modules. > > On May 15, 2008, at 12:03 PM, Hardy Ferentschik wrote: > >> 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 make sense of the exception I get during documentation >> generation: >> >> [INFO] [jdocbook:translate {execution: default}] >> [INFO] Processing translation [fr-FR] >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] FATAL ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] unable to obtain appropriate runtime environment >> CreateProcess: po2xml >> D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_ >> mapping.xml >> D:\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po >> error=2 >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Trace >> org.jboss.maven.shared.process.ExecutionException: unable to obtain >> appropriate runtime environment >> ... >> Caused by: java.io.IOException: CreateProcess: po2xml >> D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_mapping.xml >> D:\Hardy\work\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po >> error=2 >> >> >> Do your Hibernate Search changes effect the core as well? With the latest >> changes you don't have compile the core >> anymore to build Hibernate Search. All the dependencies are managed with >> ivy. Of course if your patches effect the core you will have to still do it >> ;-) JDK5 should be fine though. >> >> >> --Hardy >> >> >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > ----------------------------- > Steve Ebersole > > Project Lead > http://hibernate.org > [EMAIL PROTECTED] > > > > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
