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

> 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 maven world (e.g. not depend on the repository jar but just depend on the project to get the speed an incremental IDE can give you)

> 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 think it is a mix - i'm the "eclipse guy" on the team and I just haven't had the time to integrate with 3.3.x yet ;(

/max > 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 <steve(a)hibernate.org&gt;: >> 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(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> >> >> ----------------------------- >> Steve Ebersole >> >> Project Lead >> http://hibernate.org >> steve(a)hibernate.org >> >> >> >> >> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev >