Eclipse Community Forums: Rich Client Platform (RCP) » problem with ant builder helios

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » problem with ant builder helios

Show: Today's Messages :: Show Polls :: Message Navigator

problem with ant builder helios [message #652073]

Wed, 02 February 2011 15:09

Carmelo

Messages: 224
Registered: July 2009

Senior Member

Messaggio multiparte in formato MIME.

------=_NextPart_000_02C6_01CBC2F3.87572D70
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit

Hi all
hope someone can help me in using ant to build my rcp application.

till today I have always used the internal eclipse tool to export my rcp
application (with branding and so on).

now we need to start to integrate ant in this process.

hi have followed the example on the vogella build forum.

the example works fine on eclipse galileo ... but I cannot run the same one
on helios (sp1).

C:\IDE\eclipse-jee-helios-SR1-win32\eclipse\plugins\org.ecli pse.pde.build_3.6.1.R36x_v20100823\scripts\productBuild\prod uctBuild.xml:35:
The following error occurred while executing this line:
C:\IDE\eclipse-jee-helios-SR1-win32\eclipse\plugins\org.ecli pse.pde.build_3.6.1.R36x_v20100823\scripts\productBuild\prod uctBuild.xml:69:
Unable to find element:
E:\devel\BuildTest\workspace\org.eclipse.pde.build\buildDire ctory\features\de.vogella.build.ui2\de.vogella.build.ui.prod uct.

looks for me that there is a different approach used in searching the
product.

can someone help me to find the solution?

attached are the files used for the build
- build.properties
- build.xml

many thanks in advance
carmelo

------=_NextPart_000_02C6_01CBC2F3.87572D70
Content-Type: application/octet-stream;
name="build.properties"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="build.properties"

=09
############################################################ #############=
######
# Copyright (c) 2003, 2006 IBM Corporation and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#=20
# Contributors:
# IBM Corporation - initial API and implementation
############################################################ #############=
######
product=3D/de.vogella.build.ui2/de.vogella.build.ui.product
runPackager=3Dtrue

p2.gathering=3Dtrue
p2.metadata.repo=3Dfile:${builder}/repository
p2.artifact.repo=3Dfile:${builder}/repository

#Set the name of the archive that will result from the product build.
#archiveNamePrefix=3D

# The prefix that will be used in the generated archive.
archivePrefix=3Dyourproduct

# The location underwhich all of the build output will be collected.
collectingFolder=3D${archivePrefix}

# The list of {os, ws, arch} configurations to build. This=20
# value is a '&' separated list of ',' separate triples. For example,=20
# configs=3Dwin32,win32,x86 & linux,motif,x86
# By default the value is *,*,*
configs =3D win32, win32, x86
#configs=3Dwin32, win32, x86 & \
# linux, gtk, ppc &\
# linux, gtk, x86 & \
# linux, gtk, x86_64 & \
# linux, motif, x86 & \
# solaris, motif, sparc & \
# solaris, gtk, sparc & \
# aix, motif, ppc & \
# hpux, motif, PA_RISC & \
# macosx, carbon, ppc

#Allow cycles involving at most one bundle that needs to be compiled =
with the rest being binary bundles.
allowBinaryCycles =3D true

# Type of build. Used in naming the build output. Typically this value =
is
# one of I, N, M, S, ...
buildType=3DI

# ID of the build. Used in naming the build output.
buildId=3DTestBuild

# Label for the build. Used in naming the build output
buildLabel=3D${buildType}.${buildId}

# Timestamp for the build. Used in naming the build output
timestamp=3D007

#this property indicates whether the resolution should be done in =
development mode (i.e. ignore multiple bundles with singletons)
resolution.devMode=3Dfalse

skipBase=3Dtrue
skipMaps=3Dtrue
skipFetch=3Dtrue

############# JAVA COMPILER OPTIONS ##############
# For this example:
# We specify the JRE locations for CDC-1.1/Foundation-1.1 and J2SE-1.5
# because these are the required execution environments defined for the=20
# bundles in the example.=20

# The location of the Java jars to compile against. Typically the =
rt.jar for your JDK/JRE
#bootclasspath=3D${java.home}/lib/rt.jar

# If using an IBM VM, use
#bootclasspath=3D${java.home}/lib/core.jar;${java.home}/lib/ vm.jar

# specific JRE locations to compile against. These values are used to =
compile bundles specifying a=20
# Bundle-RequiredExecutionEnvironment. Uncomment and set values for =
environments that you support
#CDC-1.0/Foundation-1.0=3D /path/to/rt.jar
CDC-1.1/Foundation-1.1=3D${java.home}/lib/rt.jar
#OSGi/Minimum-1.0=3D
#OSGi/Minimum-1.1=3D
#JRE-1.1=3D
#J2SE-1.2=3D
#J2SE-1.3=3D
#J2SE-1.4=3D
#J2SE-1.5=3D${java.home}/lib/rt.jar
JavaSE-1.6=3D${java.home}/lib/rt.jar
#PersonalJava-1.1=3D
#PersonalJava-1.2=3D
#CDC-1.0/PersonalBasis-1.0=3D
#CDC-1.0/PersonalJava-1.0=3D
#CDC-1.1/PersonalBasis-1.1=3D
#CDC-1.1/PersonalJava-1.1=3D

# Specify the output format of the compiler log when eclipse jdt is used
logExtension=3D.log

# Whether or not to include debug info in the output jars
javacDebugInfo=3Dfalse=20

# Whether or not to fail the build if there are compiler errors
javacFailOnError=3Dtrue

# Enable or disable verbose mode of the compiler
javacVerbose=3Dtrue

# Extra arguments for the compiler. These are specific to the java =
compiler being used.
#compilerArg=3D

# Default value for the version of the source code. This value is used =
when compiling plug-ins that do not set the =
Bundle-RequiredExecutionEnvironment or set javacSource in =
build.properties
#javacSource=3D1.3

# Default value for the version of the byte code targeted. This value is =
used when compiling plug-ins that do not set the =
Bundle-RequiredExecutionEnvironment or set javacTarget in =
build.properties.
#javacTarget=3D1.1

------=_NextPart_000_02C6_01CBC2F3.87572D70
Content-Type: text/xml;
name="build.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="build.xml"

<project default=3D"main">
<property file=3D"build.properties"/>
<target name=3D"main">
<property name=3D"baseLocation" value=3D"${eclipse.home}"/>

<property name=3D"deltapack" =
value=3D"${eclipse.home}/deltapack/eclipse"/>


<available property=3D"haveDeltaPack" file=3D"${deltapack}"/>
<fail unless=3D"haveDeltaPack" message=3D"The deltapack is required to =
build
this product. Please edit buildProduct.xml or set the =
"deltapack"
property." />

<property name=3D"builder" value=3D"${basedir}" />
<property name=3D"buildDirectory" =
value=3D"${basedir}/buildDirectory"/>
<property name=3D"pluginPath"
value=3D"${basedir}/..${path.separator}${deltapack}" />
<property name=3D"buildTempFolder" value=3D"${buildDirectory}" />

<ant =
antfile=3D"${eclipse.pdebuild.scripts}/productBuild/productBuild.xml "
/>

<move todir=3D"${basedir}">
<fileset dir=3D"${buildDirectory}/${buildLabel}" includes=3D"*.zip"/>
</move>


<eclipse.convertPath fileSystemPath=3D"${basedir}" =
property=3D"resourcePath"/>
<eclipse.refreshLocal resource=3D"${resourcePath}" =
depth=3D"infinite"/>
</target>
</project>

------=_NextPart_000_02C6_01CBC2F3.87572D70--

Report message to a moderator

Re: problem with ant builder helios [message #652102 is a reply to message #652073]

Wed, 02 February 2011 16:30

Carmelo

Messages: 224
Registered: July 2009

Senior Member

sorry the example is working fine ... I did put a wrong path ... but when I
try to apply the same example to my rcp (more complex and more dependencies)
it complains with some errors :(

Buildfile: E:\depot\head\server\wb\workbench\WorkbenchBuild\build.xml

main:

main:

preBuild:

preSetup:

checkLocalMaps:

getMapFiles:

postSetup:

checkLocalBase:

getBaseComponents:

processRepos:

generateFeature:

BUILD FAILED
E:\depot\head\server\wb\workbench\WorkbenchBuild\build.xml:1 7: The following
error occurred while executing this line:
C:\IDE\eclipse-jee-helios-SR1-win32\eclipse\plugins\org.ecli pse.pde.build_3.6.1.R36x_v20100823\scripts\productBuild\prod uctBuild.xml:35:
The following error occurred while executing this line:
C:\IDE\eclipse-jee-helios-SR1-win32\eclipse\plugins\org.ecli pse.pde.build_3.6.1.R36x_v20100823\scripts\productBuild\prod uctBuild.xml:69:
Unable to find element:
E:\depot\head\server\wb\workbench\WorkbenchBuild\buildDirect ory\features\WorkbenchPlugin\com.xxx.eom.workbench.product.

Total time: 4 seconds

looks the path is wrong ... but I cannot understand why and what is wrong.

kar

"Kar" <carmeloscala@hotmail.com> ha scritto nel messaggio
news:iibrqk$ocu$1@news.eclipse.org...
> Hi all
> hope someone can help me in using ant to build my rcp application.
>
> till today I have always used the internal eclipse tool to export my rcp
> application (with branding and so on).
>
> now we need to start to integrate ant in this process.
>
> hi have followed the example on the vogella build forum.
>
> the example works fine on eclipse galileo ... but I cannot run the same
> one
> on helios (sp1).
>
> C:\IDE\eclipse-jee-helios-SR1-win32\eclipse\plugins\org.ecli pse.pde.build_3.6.1.R36x_v20100823\scripts\productBuild\prod uctBuild.xml:35:
> The following error occurred while executing this line:
> C:\IDE\eclipse-jee-helios-SR1-win32\eclipse\plugins\org.ecli pse.pde.build_3.6.1.R36x_v20100823\scripts\productBuild\prod uctBuild.xml:69:
> Unable to find element:
> E:\devel\BuildTest\workspace\org.eclipse.pde.build\buildDire ctory\features\de.vogella.build.ui2\de.vogella.build.ui.prod uct.
>
>
> looks for me that there is a different approach used in searching the
> product.
>
> can someone help me to find the solution?
>
> attached are the files used for the build
> - build.properties
> - build.xml
>
>
> many thanks in advance
> carmelo
>
>

Report message to a moderator

Re: problem with ant builder helios [message #759208 is a reply to message #652102]

Sun, 27 November 2011 16:49

Johnson Abraham

Messages: 3
Registered: November 2011

Junior Member

Hi,
I am facing similar problem with pde build. Cannot figure out the reason behind it. I
came across your message to the forum seeking help to address the same problem. Did you figure out a fix to the issue.

I am using helio eclipse as well.

I am using the same procedure detailed by vogella Eclipse PDE build tutorial

I have pasted my build.xml and build.properties file.

=======build.properties.

product=/com.demo.dataset.client/com.demo.dataset.client.product
runPackager=true

p2.gathering=true
p2.metadata.repo=file:${builder}/repository
p2.artifact.repo=file:${builder}/repository

#Set the name of the archive that will result from the product build.
#archiveNamePrefix=

# The prefix that will be used in the generated archive.
archivePrefix=yourproduct

# The location underwhich all of the build output will be collected.
collectingFolder=${archivePrefix}

# The list of {os, ws, arch} configurations to build. This
# value is a '&' separated list of ',' separate triples. For example,
# configs=win32,win32,x86 & linux,motif,x86
# By default the value is *,*,*
#configs = win32, win32, x86
#configs=win32, win32, x86 & \
# linux, gtk, ppc &\
configs = linux, gtk, x86 &
# linux, gtk, x86_64 & \
# linux, motif, x86 & \
# solaris, motif, sparc & \
# solaris, gtk, sparc & \
# aix, motif, ppc & \
# hpux, motif, PA_RISC & \
# macosx, carbon, ppc

#Allow cycles involving at most one bundle that needs to be compiled with the rest being binary bundles.
allowBinaryCycles = true

# Type of build. Used in naming the build output. Typically this value is
# one of I, N, M, S, ...
buildType=I

# ID of the build. Used in naming the build output.
buildId=DemoTestID

# Label for the build. Used in naming the build output
buildLabel=${buildType}.${buildId}

# Timestamp for the build. Used in naming the build output
timestamp=007

#this property indicates whether the resolution should be done in development mode (i.e. ignore multiple bundles with singletons)
resolution.devMode=false

skipBase=true
skipMaps=true
skipFetch=true

############# JAVA COMPILER OPTIONS ##############
# For this example:
# We specify the JRE locations for CDC-1.1/Foundation-1.1 and J2SE-1.5
# because these are the required execution environments defined for the
# bundles in the example.

# The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
#bootclasspath=${java.home}/lib/rt.jar

# If using an IBM VM, use
#bootclasspath=${java.home}/lib/core.jar;${java.home}/lib/vm.jar

# specific JRE locations to compile against. These values are used to compile bundles specifying a
# Bundle-RequiredExecutionEnvironment. Uncomment and set values for environments that you support
#CDC-1.0/Foundation-1.0= /path/to/rt.jar
CDC-1.1/Foundation-1.1=${java.home}/lib/rt.jar
#OSGi/Minimum-1.0=
#OSGi/Minimum-1.1=
#JRE-1.1=
#J2SE-1.2=
#J2SE-1.3=
#J2SE-1.4=
#J2SE-1.5=${java.home}/lib/rt.jar
JavaSE-1.6=${java.home}/lib/rt.jar
#PersonalJava-1.1=
#PersonalJava-1.2=
#CDC-1.0/PersonalBasis-1.0=
#CDC-1.0/PersonalJava-1.0=
#CDC-1.1/PersonalBasis-1.1=
#CDC-1.1/PersonalJava-1.1=

# Specify the output format of the compiler log when eclipse jdt is used
logExtension=.log

# Whether or not to include debug info in the output jars
javacDebugInfo=true

# Whether or not to fail the build if there are compiler errors
javacFailOnError=true

# Enable or disable verbose mode of the compiler
javacVerbose=true

# Extra arguments for the compiler. These are specific to the java compiler being used.
#compilerArg=

# Default value for the version of the source code. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacSource in build.properties
#javacSource=1.3

# Default value for the version of the byte code targeted. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacTarget in build.properties.
#javacTarget=1.1

======build.xml
<project default="main">
<property file="build.properties"/>
<target name="main">
<property name="baseLocation" value="${eclipse.home}"/>

<property name="deltapack" value="${eclipse.home}/delta-package/eclipse"/>


<available property="haveDeltaPack" file="${deltapack}"/>
<echo> ${deltapack}</echo>
<fail unless="haveDeltaPack" message="The deltapack is required to build this product. Please edit buildProduct.xml or set the "deltapack" property." />

<property name="builder" value="${basedir}" />
<property name="buildDirectory" value="${basedir}/buildDirectory"/>
<property name="pluginPath" value="${basedir}/..${path.separator}${deltapack}" />
<property name="buildTempFolder" value="${buildDirectory}" />

<ant antfile="${eclipse.pdebuild.scripts}/productBuild/productBuild.xml" />

<move todir="${basedir}">
<fileset dir="${buildDirectory}/${buildLabel}" includes="*.zip"/>
</move>


<eclipse.convertPath fileSystemPath="${basedir}" property="resourcePath"/>
<eclipse.refreshLocal resource="${resourcePath}" depth="infinite"/>
</target>
</project>

thanks,
Johnson Abraham.

Report message to a moderator

Previous Topic:	How to test whether the active editor part is adaptable to something
Next Topic:	memorize window size and posotion : RCP application

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 30 14:30:30 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter