I have a <java> task that I'm using as such on two separate machines:
<java jvm="${java.bin}/java.exe"
classname="org.eclipse.core.launcher.Main"
classpath="${eclipse.home}/startup.jar"
fork="true" failonerror="true" maxmemory="512m">
<env key="Path"
path="${java.library.path}:${rcompile.home}/DLL"/>
<arg value="-noupdate"/>
<arg value="-data"/>
<arg value="${workspace.dir}"/>
<arg value="-application"/>
<arg value="com.versata.tl.studio.lightsout.runActionRunnable"/>
<arg value="-project"/>
<arg value="${project}"/>
<arg value="-action"/>
<arg
value="com.versata.tl.studio.lightsout.actions.PublishProject"/>
</java>
Up until this point, the log shows identical (version of ant, version of java,
line for line log file is identical). In fact, both machines were built
IDENTICALLY to a T. When running this task, however, one of the machines
claims:
[echo] Publishing projects to build EAR.
[java] Executing 'C:\IBM\WebSphere\AppServer\java\bin\java.exe' with
arguments:
[java] '-Xmx512m'
[java] '-classpath'
[java] 'C:\Versata\BRE-6.3\workbench\startup.jar'
[java] 'org.eclipse.core.launcher.Main'
[java] '-noupdate'
[java] '-data'
[java] 'C:/VersataWorkbench/workspace'
[java] '-application'
[java] 'com.versata.tl.studio.lightsout.runActionRunnable'
[java] '-project'
[java] 'rossApp'
[java] '-action'
[java] 'com.versata.tl.studio.lightsout.actions.PublishProject'
[java]
[java] The ' characters around the executable and arguments are
[java] not part of the command.
[java] Setting environment variable:
Path=C:\IBM\WebSphere\AppServer\java\jre\bin;C:\Versata\BRE-6.3\websphere61\VLS\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Versata\BRE-6.3\workbench\plugins\com.versata.tl.rcompile_6.3.0.0\DLL
[java] Unable to resolve VLS_LOGS_ROOT from JNDIName: null
[java] VLS_LOGS_ROOT = C:\Versata\BRE-6.3\websphere61\VLS\bin\logs
BUILD FAILED
C:\Versata\BRE-6.3\websphere61\VLS\bin\lightsout.xml:270: Java returned: 13
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.Main.runBuild(Main.java:698)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
And on the other machine, it rolls right through. Line 270 of lightsout.xml is:
fork="true" failonerror="true" maxmemory="512m">
Any help with how I can trouble-shoot this dilemma?
Thanks,
Eric
