| InvocationTargetException during headless build [message #29270] |
Fri, 24 October 2008 12:20  |
Eclipse User |
|
|
|
Originally posted by: prashanto.chatterjee.gmail.com
Hi,
I am trying to setup a headless build environment for my plugins and use a
feature as my top-element. The generated build file inside feature project
tries to build plugins in certain order. The build goes fine for the first
two plugins but fails with an InvocationTargetException for the third
plugin.
I tried looking at earlier posts and though they sound pretty close to my
problem, I dont see a resolution in sight. Most of the posts complained of
an OutOfMemoryException but that is not what is happening in my case.
The puzling thing is that the same block of code in build.xml of another
plugin works perfectly.
Below is the section inside build.xml that complains with the exception:
------------------------------------------------------------ -------
<target name="@dot" depends="init" unless="@dot" description="Create jar:
com.avaya.eventprocessor.ui.xmleditor @dot.">
<delete dir="${temp.folder}/@dot.bin"/>
<mkdir dir="${temp.folder}/@dot.bin"/>
<path id="@dot.classpath">
<pathelement
path=" D:/Prashanto/Projects/Event_Processor/Eclipse_3.4/eclipse/pl ugins/org.eclipse.ui_3.4.0.I20080610-1200.jar "/>
..
..
..
</path>
<!-- compile the source code -->
<javac destdir="${temp.folder}/@dot.bin" failonerror="${javacFailOnError}"
verbose="${javacVerbose}" debug="${javacDebugInfo}" includeAntRuntime="no"
bootclasspath="${bundleBootClasspath}" source="${bundleJavacSource}"
target="${bundleJavacTarget}" >
<compilerarg line="${compilerArg}" compiler="${build.compiler}"/>
<classpath refid="@dot.classpath" />
<src path="src/" />
<compilerarg value="@${basedir}/javaCompiler...args"
compiler="org.eclipse.jdt.core.JDTCompilerAdapter"/>
<compilerarg line="-log '${temp.folder}/@dot.bin${logExtension}'"
compiler="org.eclipse.jdt.core.JDTCompilerAdapter"/>
</javac>
------------------------------------------------------------ -------
I do have the requisite entries in the classpath. Also, when I run the ant
script seperately it does compile the plugin classes properly.
I am really at my wits end especially considering the fact that the build
ran successfully the first time (the old curse) and did generate the
deployable feature for me as a zip.
Appreciate any help in this regard,
Prashanto Chatterjee
|
|
|
| Re: InvocationTargetException during headless build [message #29309 is a reply to message #29270] |
Fri, 24 October 2008 12:59  |
| Eclipse User |
|
|
|
Originally posted by: prashanto.chatterjee.gmail.com
Drat! A silly mistake was rectified and it started working. I had created a
batch file that had:
%JAVAEXE% -jar %LAUNCHER% -application org.eclipse.ant.core.antRunner -data
%WORKSPACE% -buildfile %BUILDFILE% -Dbuilder=%BUILDDIRECTORY%
I had pointed WORKSPACE to my local eclipse workspace containing all the
features and plugins.
It seems that removing the 'data' argument fixes this problem. I guess this
was in some way interfering with the 'buildDirectory' property in the
build.properties file.
Thanks.
"Prashanto Chatterjee" <prashanto.chatterjee@gmail.com> wrote in message
news:gdseim$93m$1@build.eclipse.org...
> Hi,
> I am trying to setup a headless build environment for my plugins and use a
> feature as my top-element. The generated build file inside feature project
> tries to build plugins in certain order. The build goes fine for the first
> two plugins but fails with an InvocationTargetException for the third
> plugin.
>
> I tried looking at earlier posts and though they sound pretty close to my
> problem, I dont see a resolution in sight. Most of the posts complained of
> an OutOfMemoryException but that is not what is happening in my case.
> The puzling thing is that the same block of code in build.xml of another
> plugin works perfectly.
>
> Below is the section inside build.xml that complains with the exception:
> ------------------------------------------------------------ -------
> <target name="@dot" depends="init" unless="@dot" description="Create jar:
> com.avaya.eventprocessor.ui.xmleditor @dot.">
>
> <delete dir="${temp.folder}/@dot.bin"/>
>
> <mkdir dir="${temp.folder}/@dot.bin"/>
>
> <path id="@dot.classpath">
>
> <pathelement
> path=" D:/Prashanto/Projects/Event_Processor/Eclipse_3.4/eclipse/pl ugins/org.eclipse.ui_3.4.0.I20080610-1200.jar "/>
>
> .
>
> .
>
> .
>
> </path>
>
> <!-- compile the source code -->
>
> <javac destdir="${temp.folder}/@dot.bin" failonerror="${javacFailOnError}"
> verbose="${javacVerbose}" debug="${javacDebugInfo}" includeAntRuntime="no"
> bootclasspath="${bundleBootClasspath}" source="${bundleJavacSource}"
> target="${bundleJavacTarget}" >
>
> <compilerarg line="${compilerArg}" compiler="${build.compiler}"/>
>
> <classpath refid="@dot.classpath" />
>
> <src path="src/" />
>
> <compilerarg value="@${basedir}/javaCompiler...args"
> compiler="org.eclipse.jdt.core.JDTCompilerAdapter"/>
>
> <compilerarg line="-log '${temp.folder}/@dot.bin${logExtension}'"
> compiler="org.eclipse.jdt.core.JDTCompilerAdapter"/>
>
> </javac>
>
> ------------------------------------------------------------ -------
>
> I do have the requisite entries in the classpath. Also, when I run the ant
> script seperately it does compile the plugin classes properly.
>
> I am really at my wits end especially considering the fact that the build
> ran successfully the first time (the old curse) and did generate the
> deployable feature for me as a zip.
>
> Appreciate any help in this regard,
> Prashanto Chatterjee
>
|
|
|
| Re: InvocationTargetException during headless build [message #583571 is a reply to message #29270] |
Fri, 24 October 2008 12:59 |
| Eclipse User |
|
|
|
Originally posted by: prashanto.chatterjee.gmail.com
Drat! A silly mistake was rectified and it started working. I had created a
batch file that had:
%JAVAEXE% -jar %LAUNCHER% -application org.eclipse.ant.core.antRunner -data
%WORKSPACE% -buildfile %BUILDFILE% -Dbuilder=%BUILDDIRECTORY%
I had pointed WORKSPACE to my local eclipse workspace containing all the
features and plugins.
It seems that removing the 'data' argument fixes this problem. I guess this
was in some way interfering with the 'buildDirectory' property in the
build.properties file.
Thanks.
"Prashanto Chatterjee" <prashanto.chatterjee@gmail.com> wrote in message
news:gdseim$93m$1@build.eclipse.org...
> Hi,
> I am trying to setup a headless build environment for my plugins and use a
> feature as my top-element. The generated build file inside feature project
> tries to build plugins in certain order. The build goes fine for the first
> two plugins but fails with an InvocationTargetException for the third
> plugin.
>
> I tried looking at earlier posts and though they sound pretty close to my
> problem, I dont see a resolution in sight. Most of the posts complained of
> an OutOfMemoryException but that is not what is happening in my case.
> The puzling thing is that the same block of code in build.xml of another
> plugin works perfectly.
>
> Below is the section inside build.xml that complains with the exception:
> ------------------------------------------------------------ -------
> <target name="@dot" depends="init" unless="@dot" description="Create jar:
> com.avaya.eventprocessor.ui.xmleditor @dot.">
>
> <delete dir="${temp.folder}/@dot.bin"/>
>
> <mkdir dir="${temp.folder}/@dot.bin"/>
>
> <path id="@dot.classpath">
>
> <pathelement
> path=" D:/Prashanto/Projects/Event_Processor/Eclipse_3.4/eclipse/pl ugins/org.eclipse.ui_3.4.0.I20080610-1200.jar "/>
>
> .
>
> .
>
> .
>
> </path>
>
> <!-- compile the source code -->
>
> <javac destdir="${temp.folder}/@dot.bin" failonerror="${javacFailOnError}"
> verbose="${javacVerbose}" debug="${javacDebugInfo}" includeAntRuntime="no"
> bootclasspath="${bundleBootClasspath}" source="${bundleJavacSource}"
> target="${bundleJavacTarget}" >
>
> <compilerarg line="${compilerArg}" compiler="${build.compiler}"/>
>
> <classpath refid="@dot.classpath" />
>
> <src path="src/" />
>
> <compilerarg value="@${basedir}/javaCompiler...args"
> compiler="org.eclipse.jdt.core.JDTCompilerAdapter"/>
>
> <compilerarg line="-log '${temp.folder}/@dot.bin${logExtension}'"
> compiler="org.eclipse.jdt.core.JDTCompilerAdapter"/>
>
> </javac>
>
> ------------------------------------------------------------ -------
>
> I do have the requisite entries in the classpath. Also, when I run the ant
> script seperately it does compile the plugin classes properly.
>
> I am really at my wits end especially considering the fact that the build
> ran successfully the first time (the old curse) and did generate the
> deployable feature for me as a zip.
>
> Appreciate any help in this regard,
> Prashanto Chatterjee
>
|
|
|
Powered by
FUDForum. Page generated in 0.03228 seconds
] 
Search
Help
Register
Login
Home
