[hibernate-dev] building hibernate trunk
Aleksandar Kostadinov
akostadi at redhat.com
Wed Feb 20 09:13:09 EST 2008
I see what the error is. It is trying to run po2xml but the file doesn't
exist. So I installed kdesdk package on RHEL4 and get the following error:
[INFO] [jdocbook:translate {execution: default}]
[INFO] Processing translation [es-ES]
the translation of '<entry>yes</entry>' doesn't start with a tag.
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] there was a problem executing command; check output
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.jboss.jdocbook.i18n.actions.process.ExecutionException: there was a
problem executing command; check output
at
org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:70)
at
org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:45)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.generateTranslatedXML(TranslateXmlAction.java:107)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:66)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:80)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.perform(TranslateXmlAction.java:50)
at
org.jboss.maven.plugins.jdocbook.TranslationMojo.doExecute(TranslationMojo.java:38)
at
org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:272)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Is there any plan to have a pure java solution and stop relying on
po2xml? As well how would that work on windows? And how to make it work
at all :)
This seems to be the last issue as other modules are building fine.
Thanks,
Aleksandar
Aleksandar Kostadinov wrote, On 02/20/2008 01:41 PM (EEST):
> As we talked yesterday it was the pluginRepository entries missing.
>
> Now I get the following error:
>
> [INFO] Processing translation [es-ES]
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] unable to obtain appropriate runtime environment
> java.io.IOException: po2xml: not found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.jboss.jdocbook.i18n.actions.process.ExecutionException: unable to
> obtain appropriate runtime environment
> at
> org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:74)
> at
> org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:45)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.generateTranslatedXML(TranslateXmlAction.java:107)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:66)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:80)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.perform(TranslateXmlAction.java:50)
> at
> org.jboss.maven.plugins.jdocbook.TranslationMojo.doExecute(TranslationMojo.java:38)
> at
> org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:272)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.io.IOException: java.io.IOException: po2xml: not found
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
> at java.lang.ProcessImpl.start(ProcessImpl.java:65)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
> at java.lang.Runtime.exec(Runtime.java:591)
> at java.lang.Runtime.exec(Runtime.java:429)
> at java.lang.Runtime.exec(Runtime.java:326)
> at
> org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:60)
> ... 25 more
>
> Any ideas?
>
> Thanks,
> Aleksandar
>
> Steve Ebersole wrote, On 02/19/2008 07:33 PM (EEST):
>> Are you enabling the snapshot repo?
>>
>> The built artifact is certainly there...
>> http://snapshots.jboss.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plugin/2.1.0-SNAPSHOT/
>>
>>
>> On Feb 19, 2008, at 10:56 AM, Aleksandar Kostadinov wrote:
>>
>>> Hello
>>>
>>> How can one build hibernate trunk?
>>>
>>> I tried to checkout
>>> http://anonsvn.jboss.org/repos/hibernate/core/trunk/
>>> Then first run mvn install on
>>> http://anonsvn.jboss.org/repos/hibernate/maven-poms/trunk/core-parent/pom.xml
>>>
>>> and then mvn install in the checkout dir but I get:
>>>
>>> ...
>>> WAGON_VERSION: 1.0-beta-2
>>> [INFO] snapshot
>>> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.0-SNAPSHOT: checking
>>> for updates from snapshots.jboss.org
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Plugin could not be found - check that the goal name is correct:
>>> Unable to download the artifact from any repository
>>> ...
>>>
>>> Can we have everything needed to build it in snapshots.jboss.org?
>>>
>>> Thanks much,
>>> Aleksandar
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>> -----------------------------
>> Steve Ebersole
>>
>> Project Lead
>> http://hibernate.org
>> steve at hibernate.org
>>
>>
>>
>>
>
More information about the hibernate-dev
mailing list