查看新闻/公告--[整理]使用Ant调用PDE自动Build RCP Application。

source.. = src/
output.. = bin/
bin.includes = plugin.xml,\
               META-INF/,\
               .,\
               icons/,\
               about.gif,\
               splash1.bmp,\
               lib/xxx.jar,\
               introContent.xml,\
               script/,\
               splash.bmp,\
               template/,\
               content/
jars.extra.classpath = lib/xxx.jar
##########################################################
# 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
#
# Contributors:
#     IBM Corporation – initial API and implementation
##########################################################
# 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

############# PLUG-IN VERSIONS ######################

#Plug-in的工程名
rcp.plugin=mainframe

#Feature的工程名，因为没有Feature，就随便写了个名字
feature.plugin=mainframe.feature

# PDE Build的版本
# 实际就是plugins目录下有个类似org.eclipse.pde.build_3.6.1.R36x_v20100823\的文件夹
# 要后面那堆数字什么的。
pdeBuildPluginVersion=3.6.1.R36x_v20100823

# equinox.launcher的版本
# 同上，plugins目录下有个org.eclipse.equinox.launcher_1.1.0.v20100507.jar文件
equinoxLauncherPluginVersion=1.1.0.v20100507

############# BASE LOCATION #########################
# 目标平台的Base目录，外部传入绝对路径
base=

############# ECLIPSE LOCATION ######################
# Eclipse 安装目录，以调用PDE.
#eclipse的路径用相对路径，不好使，所以从命令行传入绝对路径。
eclipseLocation=

############# PRODUCT/PACKAGING CONTROL #############
product=/mainframe/mainframe.product
runPackager=true

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

# 压缩包名字前缀.
archivePrefix=mainframe

# 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 = *, *, *
configs=win32, win32, x86
# & \
#    win32,win32,x86_64 & \
#    win32,win32,wpf & \
#    linux, gtk, ppc & \
#    linux, gtk, x86 & \
#    linux, gtk, x86_64 & \
#    linux, motif, x86 & \
#    solaris, motif, sparc & \
#    solaris, gtk, sparc & \
#    aix, motif, ppc & \
#    hpux, motif, ia64_32 & \
#    macosx, carbon, ppc & \
#    macosx, carbon, x86 & \
#    macosx, cocoa, ppc & \
#    macosx, cocoa, x86 & \
#    macosx, cocoa, x86_64

# By default PDE creates one archive (result) per entry listed in the configs property.
# Setting this value to true will cause PDE to only create one output containing all
# artifacts for all the platforms listed in the configs property.
# To control the output format for the group, add a "group, group, group – <format>" entry to the
# archivesFormat.
#groupConfigurations=true

#The format of the archive. By default a zip is created using antZip.
#The list can only contain the configuration for which the desired format is different than zip.
#archivesFormat=win32, win32, x86 – antZip& \
#    linux, gtk, ppc – antZip &\
#    linux, gtk, x86 – antZip& \
#    linux, gtk, x86_64 – antZip& \
# linux, motif, x86 – antZip& \
#    solaris, motif, sparc – antZip& \
#    solaris, gtk, sparc – antZip& \
#    aix, motif, ppc – antZip& \
#    hpux, motif, PA_RISC – antZip& \
#    macosx, carbon, ppc – antZip

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

#Sort bundles depenedencies across all features instead of just within a given feature.
flattenDependencies = true

#Parallel compilation, requires flattenedDependencies=true
#parallelCompilation=true
#parallelThreadCount=
#parallelThreadsPerProcessor=

#Set to true if you want the output to be ready for an update jar (no site.xml generated)
#outputUpdateJars = false

#Set to true for Jnlp generation
#codebase should be a URL that will be used as the root of all relative URLs in the output.
#generateJnlp=false
#jnlp.codebase=<codebase url>
#jnlp.j2se=<j2se version>
#jnlp.locale=<a locale>
#jnlp.generateOfflineAllowed=true or false generate <offlineAllowed/> attribute in the generated features
#jnlp.configs=${configs}            #uncomment to filter the content of the generated jnlp files based on the configuration being built

#Set to true if you want to sign jars
#signJars=false
#sign.alias=<alias>
#sign.keystore=<keystore location>
#sign.storepass=<keystore password>
#sign.keypass=<key password>

#Arguments to send to the zip executable
zipargs=

#Arguments to send to the tar executable
tarargs=

#Control the creation of a file containing the version included in each configuration – on by default
#generateVersionsLists=false

############## BUILD NAMING CONTROL ################
# Build目录，外部传入
buildDirectory=

# Build类型，一般是I, N, M, S, 什么的
buildType=I

# 输出的名字.
buildId=mainframe

# 输出目录名，结果里面会有个类似Imainframe这个目录
buildLabel=${buildType}.${buildId}

# 时间戳
timestamp=007

#The value to be used for the qualifier of a plugin or feature when you want to override the value computed by pde.
#The value will only be applied to plugin or features indicating build.properties, qualifier = context
#forceContextQualifier=<the value for the qualifier>

#Enable / disable the generation of a suffix for the features that use .qualifier.
#The generated suffix is computed according to the content of the feature
#generateFeatureVersionSuffix=true

############# BASE CONTROL #############
# Settings for the base Eclipse components and Java class libraries
# against which you are building.
# Base location for anything the build needs to compile against.  For example,
# in most RCP app or a plug-in,  the baseLocation should be the location of a previously
# installed Eclipse against which the application or plug-in code will be compiled and the RCP delta pack.

###就是eclipse-RCP-3.3.2-delta-pack和eclipse-RCP-3.3.2-win32的解压位置
baseLocation=${base}/target/eclipse

#Folder containing repositories whose content is needed to compile against
#repoBaseLocation=${base}/repos
#Folder where the content of the repositories from ${repoBaseLocation} will be made available as a form suitable to be compiled against
#transformedRepoLocation=${base}/transformedRepos

#Os/Ws/Arch/nl of the eclipse specified by baseLocation
baseos=win32
basews=win32
basearch=x86

#this property indicates whether you want the set of plug-ins and features to be considered during the build to be limited to the ones reachable from the features / plugins being built
filteredDependencyCheck=false

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

#pluginPath is a list of locations in which to find plugins and features.  This list is separated by the platform file separator (; or :)
#a location is one of:
#- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo
#- a directory that contains a /plugins or /features subdirectory
#- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml
#pluginPath=

skipBase=true
eclipseURL=<url for eclipse download site>
eclipseBuildId=<Id of Eclipse build to get>
eclipseBaseURL=${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip

############# MAP FILE CONTROL ################
# This section defines CVS tags to use when fetching the map files from the repository.
# If you want to fetch the map file from repository / location, change the getMapFiles target in the customTargets.xml

skipMaps=true
mapsRepo=:pserver:anonymous@example.com/path/to/repo
mapsRoot=path/to/maps
mapsCheckoutTag=HEAD

#tagMaps=true
mapsTagTag=v${buildId}

############ REPOSITORY CONTROL ###############
# 从CVS、SVN之类的地方获取代码.
# 例子：fetchTag=CVS=HEAD, SVN=v20050101
# fetchTag=HEAD
skipFetch=true

############# JAVA COMPILER OPTIONS ##############
# JDK/JRE的rt.jar的路径
#bootclasspath=${java.home}/lib/rt.jar

# 各种JRE 的路径. 通过Bundle-RequiredExecutionEnvironment指定的时候，就用下边这些了.
# 用哪个，就把哪行去掉注释，改改。
#CDC-1.0/Foundation-1.0= /path/to/rt.jar
#CDC-1.1/Foundation-1.1=
#OSGi/Minimum-1.0=
#OSGi/Minimum-1.1=
#JRE-1.1=
#J2SE-1.2=
#J2SE-1.3=
#J2SE-1.4=
#J2SE-1.5=
#JavaSE-1.6=
#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=

# 编译LOG的后缀名
logExtension=.log

# 在生成的jar里是否包含调试信息
javacDebugInfo=false

# 有编译错误的时候是否失败
javacFailOnError=true

# 是否开启编译器的详细模式，会输出啰嗦的LOG
javacVerbose=true

# 传给java编译器的参数
compilerArg=-encoding UTF-8 -nowarn

# 源代码的默认版本. 没有设置Bundle-RequiredExecutionEnvironment的时候，用这个值
javacSource=1.6

# 生成目标版本. 没有设置Bundle-RequiredExecutionEnvironment的时候，用这个值
javacTarget=1.6