- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
你如何将 ant 脚本转换为 gradle 脚本?
你好,
你能帮我把 ant 脚本转换成 gradle 脚本吗?我是 gradle 的新用户。
<property name="pm-dir" value="${PM-DIR}/${BUILD_NUM}" />
<property name="leis-dir" value="${LEIS_DIR}/${BUILD_NUM}" />
<property name="proxy-name" value="${PROXY_JAR_NAME}"/>
<property name="proxy-client-name" value="${PROXY_CLIENT_JAR_NAME}"/>
<property environment="env"/>
<property name="java-home" value="${env.JAVA_HOME}"/>
<condition property="build-pm">
<equals arg1="True" arg2="${BUILD_PM}" />
</condition>
<condition property="build-LEIS">
<equals arg1="True" arg2="${BUILD_LEIS}" />
</condition>
<target name="build-LEIS-components" if="build-LEIS">
<ant antfile="build.xml"
target="clean"
dir="${leis-dir}/LEIS"
inheritAll="false"/>
<ant antfile="build.xml"
target="ejbdoclet"
dir="${leis-dir}/LEIS/BusinessServices"
inheritAll="false"/>
<ant antfile="build.xml"
target="jar"
dir="${leis-dir}/LEIS"
inheritAll="false"/>
<ant antfile="build.xml"
target="clean"
dir="${leis-dir}/ETS/trunk/Entitlements"
inheritAll="false"/>
<ant antfile="build.xml"
target="build"
dir="${leis-dir}/ETS/trunk/Entitlements"
inheritAll="false"/>
<mkdir dir="${leis-dir}/JARS/APP-INF/lib/"/>
<jar jarfile="${leis-dir}/JARS/APP-INF/lib/LEISConfig.jar">
<fileset dir="LEIS/" includes="datetime.properties"/>
<fileset dir="LEIS/" includes="log4j.properties"/>
<manifest>
<attribute name="Built-By" value="${user.name}"/>
</manifest>
</jar>
</target>
<!--========================================================================
Builds pm using the supplied RE build files, modified by us.
========================================================================-->
<target name="build-pm" if="build-pm">
<!-- SPPResourceBundle Overrides -->
<mkdir dir="${pm-dir}/pm2/deploy/propertyoverrides"/>
<copy todir="${pm-dir}/pm2/deploy/propertyoverrides" overwrite="true">
<fileset dir="olwpmconfig/propertyoverrides"/>
</copy>
<!-- copy build.properties into pm dir, complete with kodo key -->
<copy file="olwpmconfig/build.properties" todir="${pm-dir}/pm2/" overwrite="true">
<filterchain>
<replacetokens>
<token key="LOGGINGFLOOR" value="${PERFORMANCE_LOGGING_FLOOR}"/>
<token key="BEADIR" value="${BEA_HOME}"/>
</replacetokens>
</filterchain>
</copy>
<!--the actual Retail Express build scripts to create the pm-main.ear-->
<echo message="Calling pm Build Script"/>
<ant antfile='${pm-dir}/pm2/build/build.xml' target='clean-build' inheritAll="false"/>
<!--delete the extra copy of jdo.dtd-->
<delete file="jdo.dtd" />
<fileset id="required-pm-client-libs" dir="${pm-dir}/pm2/deploy/lib">
<include name="*.jar"/>
<include name="client/*.jar"/>
<exclude name="*tests.jar"/>
</fileset>
<!-- Used to populate value of MANIFEST.MF Class-path attribute. Turns our set of "required" libs
into a nice space separated string to place in the MANIFEST.MF. Property is used in the "dist"
task's jar command. -->
<pathconvert property="client-classpath"
refid="required-pm-client-libs"
pathsep=" "
dirsep="/">
<map from="${pm-dir}/pm2/deploy/lib/" to=""/>
</pathconvert>
<jar update="true" jarfile="${pm-dir}/pm2/deploy/lib/pm-core.jar">
<manifest>
<attribute name="Class-Path" value="${client-classpath}"/>
<attribute name="Main-Class" value="com.retailexp.pm.ui.util.SPPClientStartUp"/>
</manifest>
</jar>
<!-- Creates a file Marimba/BigFix/WhatEver can use to track the version of pm installed on a machine -->
<echo message="${pm_MAJOR_VERSION}.${BUILD_NUM}" file="${pm-dir}/pm2/deploy/lib/version.txt" append="false"/>
<!-- Remove files we place on classpath from ears, Mantis 10624 -->
<!-- pm -->
<move file="${pm-dir}/pm2/deploy/dist/pm-main.ear" tofile="${pm-dir}/pm2/deploy/dist/old-pm-main.ear"/>
<unzip src="${pm-dir}/pm2/deploy/dist/old-pm-main.ear" dest="${pm-dir}/pm2/deploy/dist/">
<patternset>
<include name="lib/pm-server-conf.jar"/>
</patternset>
</unzip>
<move file="${pm-dir}/pm2/deploy/dist/lib/pm-server-conf.jar" tofile="${pm-dir}/pm2/deploy/dist/lib/old-pm-server-conf.jar"/>
<zip file="${pm-dir}/pm2/deploy/dist/lib/pm-server-conf.jar">
<zipfileset src="${pm-dir}/pm2/deploy/dist/lib/old-pm-server-conf.jar">
<exclude name="log4j.properties"/>
<exclude name="ehcache-transactional.xml"/>
</zipfileset>
</zip>
<zip file="${pm-dir}/pm2/deploy/dist/pm-main.ear">
<zipfileset src="${pm-dir}/pm2/deploy/dist/old-pm-main.ear">
<exclude name="lib/pm-server-conf.jar"/>
</zipfileset>
<zipfileset dir="${pm-dir}/pm2/deploy/dist/lib/" includes="pm-server-conf.jar" fullpath="lib/pm-server-conf.jar"/>
</zip>
<!-- EDM -->
<move file="${pm-dir}/pm2/deploy/dist/pm-edm.ear" tofile="${pm-dir}/pm2/deploy/dist/old-pm-edm.ear"/>
<unzip src="${pm-dir}/pm2/deploy/dist/old-pm-edm.ear" dest="${pm-dir}/pm2/deploy/dist/">
<patternset>
<include name="lib/pm-server-conf.jar"/>
</patternset>
</unzip>
<move file="${pm-dir}/pm2/deploy/dist/lib/pm-server-conf.jar" tofile="${pm-dir}/pm2/deploy/dist/lib/old-pm-server-conf.jar"/>
<zip file="${pm-dir}/pm2/deploy/dist/lib/pm-server-conf.jar">
<zipfileset src="${pm-dir}/pm2/deploy/dist/lib/old-pm-server-conf.jar">
<exclude name="log4j.properties"/>
</zipfileset>
</zip>
<zip file="${pm-dir}/pm2/deploy/dist/pm-edm.ear">
<zipfileset src="${pm-dir}/pm2/deploy/dist/old-pm-edm.ear">
<exclude name="lib/pm-server-conf.jar"/>
</zipfileset>
<zipfileset dir="${pm-dir}/pm2/deploy/dist/lib/" includes="pm-server-conf.jar" fullpath="lib/pm-server-conf.jar"/>
</zip>
</target>
<!--========================================================================
Builds LEIS
========================================================================-->
<target name="build-proxy" if="build-LEIS">
<!--copy deploy.properties with the proper jar names and locations-->
<copy file="LEIS/deploy.properties" todir="${leis-dir}/proxy/config/build/" overwrite="true">
<filterchain>
<replacetokens>
<token key="pmCORE" value="${pm_CORE_NAME}"/>
<token key="pmTRANSFER" value="${pm_TRANSFER_NAME}"/>
<token key="PROXYJARNAME" value="${PROXY_JAR_NAME}"/>
<token key="PROXYCLIENTJARNAME" value="${PROXY_CLIENT_JAR_NAME}"/>
<token key="PROXYLIBSDIR" value="${leis-dir}/JARS/"/>
</replacetokens>
</filterchain>
</copy>
<ant antfile="build.xml" target="clean" dir="${leis-dir}/proxy" inheritAll="false" />
<ant antfile="build.xml" target="prod-dist" dir="${leis-dir}/proxy" inheritAll="false">
<property name="build.name" value="${pm_MAJOR_VERSION}.${BUILD_NUM}"/>
</ant>
<ear destfile="${ear-name}" appxml="LEIS/application.xml">
<metainf dir="${leis-dir}/LEIS/conf/EAR/META-INF" includes="weblogic-application.xml"/>
<fileset dir="${leis-dir}/JARS/" includes="*.jar"/>
<fileset dir="${leis-dir}/JARS/" includes="APP-INF/**" excludes="APP-INF/lib/wlfullclient.jar"/>
</ear>
<!-- Place the proxy-client jar in the pm ear-->
<zip update="true" destfile="${pm-dir}/pm2/deploy/dist/pm-main.ear">
<zipfileset dir="${leis-dir}/proxy/dist/" includes="${proxy-client-name}" fullpath="APP-INF/lib/${proxy-client-name}"/>
</zip>
</target>
<target name="build-cpc">
<copy file="${pm-dir}/pm2/deploy/lib/${pm_TRANSFER_NAME}" todir="${leis-dir}/cpc-web-app/webapp/lib/cpc"/>
<ant antfile="build.xml" target="build-all-environments" dir="${leis-dir}/cpc-web-app/webapp" inheritAll="false"/>
</target>
<target name="build-all">
<antcall target="build-LEIS-components"/>
<antcall target="build-pm"/>
<antcall target="build-proxy"/>
<antcall target="build-cpc"/>
</target> </condition>
<condition property="build-LEIS">
<equals arg1="True" arg2="${BUILD_LEIS}" />
</condition>
<target name="build-LEIS-components" if="build-LEIS">
<!--Go through and build the LEIS modules-->
<ant antfile="build.xml"
target="clean"
dir="${leis-dir}/LEIS"
inheritAll="false"/>
<ant antfile="build.xml"
target="ejbdoclet"
dir="${leis-dir}/LEIS/BusinessServices"
inheritAll="false"/>
<ant antfile="build.xml"
target="jar"
dir="${leis-dir}/LEIS"
inheritAll="false"/>
<ant antfile="build.xml"
target="clean"
dir="${leis-dir}/ETS/trunk/Entitlements"
inheritAll="false"/>
<ant antfile="build.xml"
target="build"
dir="${leis-dir}/ETS/trunk/Entitlements"
inheritAll="false"/>
<mkdir dir="${leis-dir}/JARS/APP-INF/lib/"/>
<jar jarfile="${leis-dir}/JARS/APP-INF/lib/LEISConfig.jar">
<fileset dir="LEIS/" includes="datetime.properties"/>
<fileset dir="LEIS/" includes="log4j.properties"/>
<manifest>
<attribute name="Built-By" value="${user.name}"/>
</manifest>
</jar>
</target>
<target name="build-pm" if="build-pm">
<mkdir dir="${pm-dir}/amp2/deploy/propertyoverrides"/>
<copy todir="${pm-dir}/amp2/deploy/propertyoverrides" overwrite="true">
<fileset dir="olwAMPconfig/propertyoverrides"/>
</copy>
<ant antfile='${pm-dir}/amp2/build/build.xml' target='clean-build' inheritAll="false"/>
<!--delete the extra copy of jdo.dtd-->
<delete file="jdo.dtd" />
<fileset id="required-amp-client-libs" dir="${pm-dir}/amp2/deploy/lib">
<include name="*.jar"/>
<include name="client/*.jar"/>
<exclude name="*tests.jar"/>
</fileset>
<!-- Used to populate value of MANIFEST.MF Class-path attribute. Turns our set of "required" libs
into a nice space separated string to place in the MANIFEST.MF. Property is used in the "dist"
task's jar command. -->
<pathconvert property="client-classpath"
refid="required-amp-client-libs"
pathsep=" "
dirsep="/">
<map from="${pm-dir}/amp2/deploy/lib/" to=""/>
</pathconvert>
<jar update="true" jarfile="${pm-dir}/amp2/deploy/lib/amp-core.jar">
<manifest>
<attribute name="Class-Path" value="${client-classpath}"/>
<attribute name="Main-Class" value="com.retailexp.amp.ui.util.SPPClientStartUp"/>
</manifest>
</jar>
<!-- Creates a file Marimba/BigFix/WhatEver can use to track the version of AMP installed on a machine -->
<echo message="${AMP_MAJOR_VERSION}.${BUILD_NUM}" file="${pm-dir}/amp2/deploy/lib/version.txt" append="false"/>
<!-- Remove files we place on classpath from ears, Mantis 10624 -->
<!-- AMP -->
<move file="${pm-dir}/amp2/deploy/dist/amp-main.ear" tofile="${pm-dir}/amp2/deploy/dist/old-amp-main.ear"/>
<unzip src="${pm-dir}/amp2/deploy/dist/old-amp-main.ear" dest="${pm-dir}/amp2/deploy/dist/">
<patternset>
<include name="lib/amp-server-conf.jar"/>
</patternset>
</unzip>
<move file="${pm-dir}/amp2/deploy/dist/lib/amp-server-conf.jar" tofile="${pm-dir}/amp2/deploy/dist/lib/old-amp-server-conf.jar"/>
<zip file="${pm-dir}/amp2/deploy/dist/lib/amp-server-conf.jar">
<zipfileset src="${pm-dir}/amp2/deploy/dist/lib/old-amp-server-conf.jar">
<exclude name="log4j.properties"/>
<exclude name="ehcache-transactional.xml"/>
</zipfileset>
</zip>
<zip file="${pm-dir}/amp2/deploy/dist/amp-main.ear">
<zipfileset src="${pm-dir}/amp2/deploy/dist/old-amp-main.ear">
<exclude name="lib/amp-server-conf.jar"/>
</zipfileset>
<zipfileset dir="${pm-dir}/amp2/deploy/dist/lib/" includes="amp-server-conf.jar" fullpath="lib/amp-server-conf.jar"/>
</zip>
<!-- EDM -->
<move file="${pm-dir}/amp2/deploy/dist/amp-edm.ear" tofile="${pm-dir}/amp2/deploy/dist/old-amp-edm.ear"/>
<unzip src="${pm-dir}/amp2/deploy/dist/old-amp-edm.ear" dest="${pm-dir}/amp2/deploy/dist/">
<patternset>
<include name="lib/amp-server-conf.jar"/>
</patternset>
</unzip>
<move file="${pm-dir}/amp2/deploy/dist/lib/amp-server-conf.jar" tofile="${pm-dir}/amp2/deploy/dist/lib/old-amp-server-conf.jar"/>
<zip file="${pm-dir}/amp2/deploy/dist/lib/amp-server-conf.jar">
<zipfileset src="${pm-dir}/amp2/deploy/dist/lib/old-amp-server-conf.jar">
<exclude name="log4j.properties"/>
</zipfileset>
</zip>
<zip file="${pm-dir}/amp2/deploy/dist/amp-edm.ear">
<zipfileset src="${pm-dir}/amp2/deploy/dist/old-amp-edm.ear">
<exclude name="lib/amp-server-conf.jar"/>
</zipfileset>
<zipfileset dir="${pm-dir}/amp2/deploy/dist/lib/" includes="amp-server-conf.jar" fullpath="lib/amp-server-conf.jar"/>
</zip>
</target>
<!--=============== Builds LEIS ========================================================================-->
<target name="build-proxy" if="build-LEIS">
<ant antfile="build.xml" target="clean" dir="${leis-dir}/proxy" inheritAll="false" />
<ant antfile="build.xml" target="prod-dist" dir="${leis-dir}/proxy" inheritAll="false">
<property name="build.name" value="${AMP_MAJOR_VERSION}.${BUILD_NUM}"/>
</ant>
<!--copy the proxy jar to the LEIS jars library-->
<copy todir="${leis-dir}/JARS" flatten="true">
<fileset dir="${leis-dir}/proxy/dist/" >
<include name="${proxy-name}"/>
</fileset>
</copy>
<!--create a directory to hold the LEIS ear contents-->
<property name="ear.dir" value="${leis-dir}/bin"/>
<property name="ear-name" value="${ear.dir}/LEIS_AMP.ear"/>
<mkdir dir="${ear.dir}"/>
<!--create the ear from the directories contents-->
<ear destfile="${ear-name}" appxml="LEIS/application.xml">
<metainf dir="${leis-dir}/LEIS/conf/EAR/META-INF" includes="weblogic-application.xml"/>
<fileset dir="${leis-dir}/JARS/" includes="*.jar"/>
<fileset dir="${leis-dir}/JARS/" includes="APP-INF/**" excludes="APP-INF/lib/wlfullclient.jar"/>
</ear>
<!-- Place the proxy-client jar in the amp ear-->
<zip update="true" destfile="${pm-dir}/amp2/deploy/dist/amp-main.ear">
<zipfileset dir="${leis-dir}/proxy/dist/" includes="${proxy-client-name}" fullpath="APP-INF/lib/${proxy-client-name}"/>
</zip>
</target>
<target name="build-cpc">
<copy file="${pm-dir}/amp2/deploy/lib/${AMP_TRANSFER_NAME}" todir="${leis-dir}/cpc-web-app/webapp/lib/cpc"/>
<ant antfile="build.xml" target="build-all-environments" dir="${leis-dir}/cpc-web-app/webapp" inheritAll="false"/>
</target>
<!--========================================= Build AMP and LEIS --!>
<target name="build-all">
<antcall target="build-LEIS-components"/>
<antcall target="build-pm"/>
<antcall target="build-proxy"/>
<antcall target="build-cpc"/>
</target>
最佳答案
只需使用
ant.importBuild 'build.xml'
关于ant - 将 ant 脚本转换为 gradle 脚本,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/6326622/
在 spring-security项目,在 build.gradle文件,以下插件可用: apply plugin: 'io.spring.nohttp' apply plugin: 'locks'
我正在尝试使用gradle任务作为“与操作系统无关的shell脚本”。我在编写构建文件的逻辑时没有问题,但是我希望能够从任何文件夹中运行它。 我的第一次尝试是在路径上放置一个带有build.gradl
我在同一目录下有三个具有不同名称的build.gradle dev.build.gradle uat.build.gradle prd.build.gradle 我有4期 “gradle build”
乡亲们 有谁知道如何使用gradle与自定义的build.gradle和settings.gradle一起运行-即两者在一起? 我认为我可以有一个自定义的build.gradle文件(-b标志)-但这
Gradle 配置有两个属性,称为 dependencies和 incoming .根据我的理解,我们可以通过 Gradle 依赖 block 向配置添加依赖,如下所示: dependencies {
我正在测试将我的工件推送到 Nexus Maven 存储库。我正在使用 gradle这样做。 gradle upload有什么区别和 gradle publish ? 最佳答案 目前gradle提供了
这里有一个类似的问题:Gradle properties not being read from ~/.gradle/gradle.properties,但它不能解决我的问题。 在我看来,gradle
如何检索 Gradle 本身的版本 以编程方式从 Gradle 插件中? 最佳答案 刚刚发现可以使用任何一种方法来解决它 getProject().getGradle().getGradleVersi
2 个 gradle 项目,A 和 B,其中 A 定义了对 B 的编译依赖。为 maven 和 gradle 项目启用了 JAR 的重新映射。我试过启用和禁用自定义工具模型。我在 init.d 目录下
如何从 gradle 运行另一个 gradle 脚本。我有多个 gradle 脚本可以在 /test 下运行测试目录。 /build.gradle使用要运行的测试 gradle 文件的名称调用。例如
我已经看到了多模块项目的不同布局,其中有些项目只有一个 build.gradle。而其他项目将有 build.gradle在根和 build.gradle在每个子项目中。我想知道有什么区别以及首选哪种
我对 Gradle 生命周期有一个基本的询问。我的项目是一个多模块项目。 我注意到以下命令: ./gradlew clean bignibou-server:run 不等于运行以下两个命令按顺序运行:
我有一个项目,其中包含一个子项目,如下所示: Root Project |----gradle.build |----SubProject |----|----gradle.build 这里的子项目包
我有 gradle 项目,我想向不使用 gradle 或 maven 等构建工具的项目添加依赖项。 目录结构如下: commonfolder\ gradleProject\ b
我想创建一个类来帮助我加载不同类型的属性(local.properties,gradle.properties,$GRADLE_HOME/gradle.properties,环境变量,系统属性和自定义
我有一个多模块项目,其目录结构如下: proj |-modA |-modB |-modMain \-modSysTest 依赖项是: modB -> modA modMain -> modB modM
我正在尝试创建一个可以在 --offline 模式下工作的 gradle 项目的副本。除了一个步骤,我已经自动化了所有步骤。我无法自动将插件 jar 下载到 gradle 缓存中。 我的离线分发通过指
基本上我想这样做: Use Gradle function from other gradle file 也就是说,从另一个 gradle 脚本中调用一个函数。问题是我的 build.gradle 在
我有一个简单的 gradle 插件,我想试用一下,但我不确定如何“请求”gradle 运行我的测试 这是我要修改的 block (在我的 gradle 构建文件的顶部) buildscript {
在 Android Studio 中创建项目时,我收到以下错误消息。 Failed to import new Gradle project: Could not install Gradle dis
我是一名优秀的程序员,十分优秀!