Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] Headless product build


Hi Gabriel,
You will need for the -Dbuilder to be the folder, not the build.properties file:
-Dbuilder=C:/Users/Gabriel/Work/eclipse_tools/config

It needs to be the folder because there are other files you can put there to further customize the build.  (customTargets.xml, allElements.xml, customAssembly.xml).

The productBuild.xml has <import file="${eclipse.pdebuild.scripts}/build.xml"/>
This imports the org.eclipse.pde.build/scripts/build.xml file, at the top of that file is where you'll see us loading the builder properties file.

-Andrew



From: Gabriel Petrovay <gabipetrovay@xxxxxxxxx>
To: pde-dev <pde-dev@xxxxxxxxxxx>
Date: 04/12/2010 05:22 PM
Subject: [pde-dev] Headless product build
Sent by: pde-dev-bounces@xxxxxxxxxxx





Hi

I closely followed the information on this page:
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user/tasks/pde_product_build.htm

I am trying to headless build on Windows with Eclipse 3.5.2 a custom product.

As stated in the initial section of the build.properties file:

# Parameters describing how and where to execute the build.
# Typical users need only update the following properties:
#    baseLocation - where things you are building against are installed
#    bootclasspath - The base jars to compile against (typicaly rt.jar)
#    configs - the list of {os, ws, arch} configurations to build.
#
# Of course any of the settings here can be overridden by spec'ing
# them on the command line (e.g., -DbaseLocation=d:/eclipse


but when I run the command:
java -jar <eclipseInstall>/plugins/org.eclipse.equinox.launcher_<version>.jar
-application org.eclipse.ant.core.antRunner -buildfile
<<eclipseInstall>/plugins/org.eclipse.pde.build_<version>/scripts/productBuild/productBuild.xml>
-Dbuilder=<path to the build configuration folder>

I get:
eclipse\plugins\org.eclipse.pde.build_3.5.2.R35x_20100114\templates\headless-build\customTargets.xml:18:
java.net.MalformedURLException: no protocol: ${eclipseBaseURL}


I tested to see what properties are set by the build.properties
configuration. And it seems that none of the settings I put there are
visible in the "productBuild.xml". For example when I run:

....
<target name="main" description="the main build target">                
   <echo>${configs}</echo>
   <antcall target="preBuild" />
....

I get:
main:
    [echo] ${configs}


So the build.properties is somehow not read. Are you aware of such a problem?

I have tried the following forms of the builder property (is this
relevant after all?):
C:\Users\Gabriel\Work\eclipse_tools\config\build.properties
C:/Users/Gabriel/Work/eclipse_tools/config/build.properties
file:/C:/Users/Gabriel/Work/eclipse_tools/config/build.properties
file:/C\:/Users/Gabriel/Work/eclipse_tools/config/build.properties


--
MSc Gabriel Petrovay
Mobile: +41(0)787978034
www.28msec.com
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev




Back to the top