ant自动构建_app_内存溢出

概述一个教程 http://www.eclipse.org/articles/Article-PDE-Automation/automation.html ======================================================= 过程： 1.建立RCP工程 2.plugin.xml的依赖项，根据需要添加jar包，缺啥加啥。 2.生成.product文件，配置，添加一个教程
http://www.eclipse.org/articles/Article-PDE-automation/automation.HTML
=======================================================
过程：
1.建立RCP工程
2.plugin.xml的依赖项，根据需要添加jar包，缺啥加啥。
2.生成.product文件，配置，添加依赖的包(包括自己)，add required，缺啥加啥，等等
3.复制buildrCP.xml和build.propertIEs，修改名字什么的。

========================================================
看下目录结构：
-----------------------------
│  run_MainFrame.bat
│
├─buildEnv
│  ├─ant
│  ├─eclipse
│  ├─jdk1.6.0_17
│  └─RCP-build-require
│      └─target
├─buildresult
│  ├─HelloWorld
│  └─mainframe
└─projectHome
    ├─HelloWolrd
    │      build.propertIEs
    │      buildrCP.xml
    └─mainframe
            build.propertIEs
            buildrCP.xml
-----------------------------
ant，就是ant的目录了。
eclipse（大Eclipse目录，平时使用的Eclipse目录，复制一个过来。
    不过，这个Eclipse是做插件开发的，应该jar包多一些吧。
    PDE Build需要使用完整的Eclipse SDK。光有几个jar包是不行的。）
RCP-build-require/target/ 放RCP Delta Pack和RCP Runtime Binary，
    把eclipse-3.6.1-delta-pack.zip和org.eclipse.rcp-3.6.1.zip解压到这里，
    后者要放到前者解压出来的eclipse目录下再解压。
    target这个目录是指你的目标平台环境，
    最好只有RCP Runtime + RCP Delta + GEF等 + 必要的一些jar包，总之越少越好吧。
    目标平台的RCP版本可以与Eclipse IDE的RCP版本不同。
buildresul，build结果所在目录，下面的目录是自动生成的
projectHome，工程目录，从Eclipse的workspace下直接把工程复制过来。
=======================================================
看一下各个文件内容：
run_MainFrame.bat

rem ---------工程名（即projectHome目录下该工程的名字），修改即可，后面不要多空格-------------
set PROJECT_name=mainframe

rem -----------------以下不用修改----------------------------
@ECHO on

rem 取得当前路径
set CURRENT_DIR=%CD%

rem 设置各种路径
set ANT_HOME=%CURRENT_DIR%\buildEnv\ant
set JAVA_HOME=%CURRENT_DIR%\buildEnv\jdk1.6.0_17
set PROJECT_HOME=%CURRENT_DIR%\projectHome\%PROJECT_name%
set ECliPSE_PATH=%CURRENT_DIR%/buildEnv/eclipse
set OUTPUT_PATH=%CURRENT_DIR%/buildresult/%PROJECT_name%
set BASE_PATH=%CURRENT_DIR%/buildEnv/RCP-build-require

rem 应该把共通参数提出来，放common.propertIEs里，放到打包程序这里。build时先copy进去
rem 这样，每个工程只设置自己相关的参数。

rem 执行build
call %ANT_HOME%\bin\ant.bat -f %PROJECT_HOME%\buildrCP.xml -DeclipseLocation=%ECliPSE_PATH% -DbuildDirectory=%OUTPUT_PATH% -Dbase=%BASE_PATH%

echo -------------------------脚本执行完毕-------------------------
pause

buildrCP.xml:

build.propertIEs，里面关于路径的字段不用修改的，就改改名字啥的就可以了。

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, 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,x86_64 & \ # win32,wpf & \ # linux, gtk, ppc & \ # linux, x86 & \ # linux, x86_64 & \ # linux, motif, x86 & \ # solaris, sparc & \ # solaris, sparc & \ # aix, ppc & \ # hpux, ia64_32 & \ # macosx, carbon, ppc & \ # macosx, 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, x86 – antZip& \ # linux, ppc – antZip &\ # linux, x86_64 – antZip& \ # linux, x86 – antZip& \ # solaris, sparc – antZip& \ # solaris, sparc – antZip& \ # aix, ppc – antZip& \ # hpux, PA_RISC – antZip& \ # macosx, 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 以下是一些经验总结： ======================================= 运行，报一个jar包找不到，把缺少的org.eclipse.core.runtime.compatibility.registry_3.3.0.v20100520.jar 放到D:\RCP_pack\buildEnv\RCP-build-require\target\eclipse\plugins目录下。只要是jar包找不到，就往这个目录放。 =============================== 路径相关的变量，路径里面用/，而不是\。 ======================================================== 遭遇让人郁闷的错误，Missing required plug-in [java] BUILD Failed [java] D:\RCP_pack\buildEnv\eclipse\plugins\org.eclipse.pde.build_3.6.1.R3 x_v20100823\scripts\productBuild\productBuild.xml:39: The following error occur ed while executing this line: [java] D:\RCP_pack\buildEnv\eclipse\plugins\org.eclipse.pde.build_3.6.1.R3 x_v20100823\scripts\productBuild\productBuild.xml:69: Bundle mainframe_1.0.0.20 102231142 Failed to resolve.: [java] Missing required plug-in org.eclipse.ui.IDe_0.0.0. [java] Missing required plug-in org.eclipse.core.resources_3.6.0. [java] Missing required plug-in org.eclipse.ui.console_3.5.0. 往RCP-build-require\target\eclipse\plugins下复制了一个ui.IDe的jar包，没反应。到处放，怎么都不行，十分郁闷。后来，干脆，把大Eclipse目录下plugins下的所有org.eclipse开头的jar包都复制过来了，竟然就没问题了。或许这样不好，但毕竟能往下跑了。基本上，只要说没找到哪个类的，就是缺jar包了。复制那一个jar包，可能还不好使。 ------------------------- 某老外Patrick说，可以让 baseLocation=${eclipseLocation} 也就是不用RCP-build-require/target下的eclipse目录，而用大Eclipse目录，会简单一些，但是不好，这样就和大eclipse环境依赖起来了。试了下，确实可以，不过，我上步已经搞定了（不过，也复制了N多jar包），所以不需要这么做了。 ====================================================== [java] [eclipse.buildScript] Bundle org.eclipse.jdt.launching: [java] [eclipse.buildScript] Missing required plug-in org.eclipse.jdt .deBUG_[3.5.0,4.0.0). 这种不用理它，貌似大家都有这东西，无影响。 ====================================================== 然后，是下一个问题。 java源代码是UTF-8格式的，自动生成的build.xml里javac部分没有指定enCoding，build过程会报错。下面是D:\RCP_pack\buildresult\mainframe\plugins\mainframe\build.xml的一部分。  <javac destdir="${build.result.folder}/@dot" failonerror="${javacFailOnError}" verbose="${javacVerbose}" deBUG="${javacDeBUGInfo}" includeAntRuntime="no" bootclasspath="${bundlebootclasspath}" source="${bundleJavacSource}" target="${bundleJavacTarget}" errorProperty="compilation.error.occured" > <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 '${build.result.folder}/@dot${logExtension}'" compiler="org.eclipse.jdt.core.JDTCompilerAdapter" /> </javac> 这个build.xml是build过程中自动生成的，类似于Eclipse中，在build.propertIEs上右键/PDE Tools/Create Ant Build file，生成的内容是类似的，只是路径什么的有不同。（1）开始想这个build.xml会有个模板，可能在哪个jar包里放着，我找到它，直接在javac加上enCoding="UTF-8"就行了，搜了半天没找到。（2）后来又想，ant应该有个默认的文件编码，能否修改它呢。搜了半天，在批处理前面加了“set ANT_OPTS=-Dfile.enCoding=UTF-8”，没效果。（3）又想，堂堂的NB脚本不应该如此没有扩展性，看到 <compilerarg line="${compilerArg}" compiler="${build.compiler}"/> 感觉这个${compilerArg}应该是用来扩展用的参数，在build.xml中搜之，发现只是开头声明了一个空值，<property name="compilerArg" value=""/> 感觉，它应该是特意留的，外部可以给这个变量赋值。修改我的build.xml的<target name="pde-build">部分，追加参数<arg value="-DcompilerArg=-enCoding UTF-8" />，好使了，开心！！！ ====================================================== build结果在D:\RCP_pack\buildresult\mainframe\I.mainframe\mainframe-win32.win32.x86.zip 就是这个zip包，复制走就可以了。 bin.includes指定的那些文件不是原样复制到结果里的，是打在plugin/main...你自己的jar包里的，运行一次程序后，就放到 D:\RCP_pack\buildresult\mainframe\I.mainframe\mainframe\configuration\org.eclipse.osgi目录下了。如果生成的结果运行出错，那就是缺少jar包或其它资源文件了， jar包在plugin.xml和product的依赖里加，资源文件在bin.includes里加。 ======================================================= Any code you wish to reference in your RCP application needs to be in a plug-in project, not a basic Java project. There is no way for plug-in code to reference Java project code at runtime, even though it will appear to compile. ------------------------------- To reference your web service classes you will need to turn your Java project into a Plug-in Project (which basically means you’ll be adding a manifest.mf file). It is common to have a JAR that is used both insIDe and outsIDe of an RCP app. I usually advise people to just make the JAR into a plug-in so it can be used either way. A plug-in is really just a JAR with some extra manifest entrIEs, so it doesn’t seem like a big deal. ------------------------------ Do you mean you want to build a feature instead of a complete product? If so, see my answer to Stefanko on march 10. One thing I forgot to point out was that you need to change the PDE build script from productBuild.xml to build.xml. You can find the build.xml file one directory up from the productBuild.xml file. And here’s a newsgroup post showing how to fill in the allElements.xml file: http://dev.eclipse.org/mhonarc/Lists/pde-build-dev/msg00673.HTML ---------------------------- Try commenting out the “javacVerbose” property in your build.propertIEs file. I added “-Nowarn” to compilerArg, und it works Now. I don’t how to check “icon” folder in build.propertIEs, but I include the image file in menifest, it works Now. thanks a lot for your reply. ----------------------------- I want Now build a rcp plug-in, but not the product. how can I modify these sripts, so that I only build the plug-ins or features. 1. Comment out the product entry in the build.propertIEs file. 2. Change the PDE build script from productBuild.xml to build.xml. You can find the build.xml file one directory up from the productBuild.xml file. 3. copy allElements.xml from the org.eclipse.pde.build plug-in and replace the IDs in the file with the ID of your feature. Here is an example of a filled out allElements.xml file. http://dev.eclipse.org/mhonarc/Lists/pde-build-dev/msg00673.HTML 总结

以上是内存溢出为你收集整理的ant自动构建全部内容，希望文章能够帮你解决ant自动构建所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。

欢迎分享，转载请注明来源：内存溢出

原文地址: http://outofmemory.cn/web/1059249.html