| Switching rcp headless build (ant task) to use target platform [message #886264] |
Thu, 14 June 2012 15:19  |
Eclipse User |
|
|
|
Hi there,
i've got an existing Product build using some ant build scripts that are called by a jenkins job. Everything worked fine over some years. Now the product is evolving from eclipse 3.2-base to indigo-base. Therefore we decided to define and use a target platform.
One of the build scripts calls a headless product build (see code below).
My goal is to change the headless build to use a target platform (defined by total amount of 4 directories) instead of a single eclipse directory.
Does anybody know how to revise the ant task below to achieve this goal?
I was hoping to find something like an additional parameter to state the .target-file defining the target platform.
My target platform is placed under version control. If there is no other way, i could always copy the four different directories into one directory and work like before, but i don't think it is a very good idea to do this, do you?
Earlier today I checked the buckminster-plugin but did not get to what I want to do.
Thanks for any help or hints,
Greets Alex
<target name="build" description="generate the RCP" depends="copy-projects">
<java fork="true" jar="${eclipse.dir}/startup.jar">
<jvmarg line="-Xms512m" />
<jvmarg line="-Xmx1024m" />
<arg line="-application org.eclipse.ant.core.antRunner" />
<arg line="-buildfile ${eclipse.dir}/plugins/org.eclipse.pde.build_3.2.1.r321_v20060823/scripts/productBuild/productBuild.xml" />
<arg line="-Dbuilder=${build.config.dir}" />
<arg line="-Dproduct=/VAUDES_Application/vaudes.product" />
<arg line="-DbuildDirectory=${build.build.dir}" />
<arg line="-DbaseLocation=${eclipse.dir}" />
</java>
<touch file="${build.exe.dir}/Vaudes/odisc.exe" />
<zip update="true" duplicate="preserve" whenempty="fail" basedir="${build.exe.dir}" destfile="${build.build.dir}/I.Vaudes/Vaudes-win32.win32.x86.zip" />
<copy file="${build.build.dir}/I.Vaudes/Vaudes-win32.win32.x86.zip" todir="${application.root.dir}/build" />
</target>
|
|
|
|
| Re: Switching rcp headless build (ant task) to use target platform [message #886556 is a reply to message #886291] |
Fri, 15 June 2012 07:07  |
| Eclipse User |
|
|
|
Hi Paul,
thanks for the quick answer!
As I understand correctly, the result using the p2.repo2runnable will be a target platform copied in a given destination. This destination will have the content of my 4 source-directories and I will use the startup.jar, productBuild.xml etc. of the target platform for the task mentioned above?
I'll try and see what i can do with it.
Thanks
Alex
|
|
|
| Re: Switching rcp headless build (ant task) to use target platform [message #887844 is a reply to message #886264] |
Sun, 17 June 2012 08:24 |
| Eclipse User |
|
|
|
I think that PDE headless build doesn't support targets in same sense as
they work in PDE (IDE).
What I do in my continuous build job is to set target folder as headless
script's ${base} property (see online help for exact definition). This
property specifies folder that an application will be compiled against.
In result, it's identical to target platform purpose for not-headless
build from PDE UI.
Either way, you may also follow Paul. He's much more experienced that me
but I think that it's not an answer to what you asked us originally.
Libor
On 06/14/2012 05:19 PM, Alexander Haag wrote:
> Hi there,
>
> i've got an existing Product build using some ant build scripts that are
> called by a jenkins job. Everything worked fine over some years. Now the
> product is evolving from eclipse 3.2-base to indigo-base. Therefore we
> decided to define and use a target platform.
>
> One of the build scripts calls a headless product build (see code
> below). My goal is to change the headless build to use a target platform
> (defined by total amount of 4 directories) instead of a single eclipse
> directory.
>
> Does anybody know how to revise the ant task below to achieve this goal?
> I was hoping to find something like an additional parameter to state the
> .target-file defining the target platform.
>
> My target platform is placed under version control. If there is no other
> way, i could always copy the four different directories into one
> directory and work like before, but i don't think it is a very good idea
> to do this, do you?
> Earlier today I checked the buckminster-plugin but did not get to what I
> want to do.
>
> Thanks for any help or hints,
> Greets Alex
>
>
>
> <target name="build" description="generate the RCP"
> depends="copy-projects">
> <java fork="true" jar="${eclipse.dir}/startup.jar">
> <jvmarg line="-Xms512m" />
> <jvmarg line="-Xmx1024m" />
> <arg line="-application org.eclipse.ant.core.antRunner" />
> <arg line="-buildfile
> ${eclipse.dir}/plugins/org.eclipse.pde.build_3.2.1.r321_v20060823/scripts/productBuild/productBuild.xml"
> />
> <arg line="-Dbuilder=${build.config.dir}" />
> <arg line="-Dproduct=/VAUDES_Application/vaudes.product" />
> <arg line="-DbuildDirectory=${build.build.dir}" />
> <arg line="-DbaseLocation=${eclipse.dir}" />
> </java>
> <touch file="${build.exe.dir}/Vaudes/odisc.exe" />
> <zip update="true" duplicate="preserve" whenempty="fail"
> basedir="${build.exe.dir}"
> destfile="${build.build.dir}/I.Vaudes/Vaudes-win32.win32.x86.zip" />
> <copy file="${build.build.dir}/I.Vaudes/Vaudes-win32.win32.x86.zip"
> todir="${application.root.dir}/build" />
> </target>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03606 seconds
] 
Search
Help
Register
Login
Home
but it is resolvable by the OSGi resolver, and can be used as the target platform for a build.