blocks|key|1541416|text|设置一个名为properties.xml的ant构建文件，您应该在其中定义您想要定制的属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1541417|下面是我在项目中使用的properties.xml样板(我改编自一本关于Ant的书)：|1541418|<?xml+version="1.0"+encoding="UTF-8"?>
<project
++name="workspace-properties"
>
++<dirname
++++property="workspace-properties.basedir"
++++file="${ant.file.workspace-properties}"
++/>

++
++
++<property+environment="env"+/>

++
++<property
++++name="ant.home"
++++value="${env.ANT_HOME}"
++/>

++
++
++<property
++++name="env.COMPUTERNAME"
++++value="${env.HOSTNAME}"
++/>

++
++
++<property
++++name="user.properties.file"
++++location="${user.home}/.build.properties"
++/>

++
++
++<property+file="build.properties"+/>

++

++<property+name="myexec1"+location="/usr/bin/myexec1"/>
++<property+name="myexec2"+location="/usr/bin/myexec2"/>

</project>|code-block|syntax|javascript|1541419|这里最重要的是尽可能多地提供有用的缺省属性值，这样就永远不会有自定义的build.properties文件了。|offset|length|style|CODE|1541420|然后，只需在项目的build.xml中对该文件执行<import>操作。|1541421|<project
++name="my-project"
>
++
++<dirname
++++property="my-project.basedir"
++++file="${ant.file.my-project}"
++/>

++<import+file="${my-project.basedir}/relative/path/to/properties.xml"/>

++<target+name="using.myexec1">
++++<echo+message="myexec1=${myexec1}"/>
++</target>
</project>|1541422|如果您需要my-project中的myexec1的自定义值，只需将一个自定义平面build.properties文件放在build.xml所在的同一目录中。|1541423|build.properties文件可能如下所示：|1541424|myexec1=c:/custom/path/to/myexec1.exe|1541425|entityMap^0|0|0|0|Z|G|0|P|8|0|0|5|A|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@$K|14|L|15|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@$K|17|L|18|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|19|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1A|8|@$K|1B|L|1C|M|N]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1E|8|@]|9|@]|A|$G|H]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

Setup an ant build file called properties.xml, in which you should define the properties that you want to customize.

Here is properties.xml boilerplate I am using for my projects ( I've adapted it from one of the books on Ant ):

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;project
 name="workspace-properties"
&gt;
 &lt;dirname
 property="workspace-properties.basedir"
 file="${ant.file.workspace-properties}"
 /&gt;

 &lt;!--
 ==========================================================
 Load Environment Variables
 ==========================================================
 --&gt;
 &lt;!-- #Load environment variables --&gt;
 &lt;property environment="env" /&gt;

 &lt;!-- this is here to deal with the fact that an IntelliJ IDEA build
 has no ant home
 --&gt;
 &lt;property
 name="ant.home"
 value="${env.ANT_HOME}"
 /&gt;

 &lt;!-- get Unix hostname, and set to Windows comparable name --&gt;
 &lt;!-- #Trick to get host name x-platform --&gt;
 &lt;property
 name="env.COMPUTERNAME"
 value="${env.HOSTNAME}"
 /&gt;

 &lt;!--
 ==========================================================
 Load property files
 Note: the ordering is VERY important.
 ==========================================================
 --&gt;
 &lt;!-- #Allow even users property file to relocate --&gt;
 &lt;property
 name="user.properties.file"
 location="${user.home}/.build.properties"
 /&gt;

 &lt;!-- Load the application specific settings --&gt;
 &lt;!-- #Project specific props --&gt;
 &lt;property file="build.properties" /&gt;

 &lt;!--
 ==========================================================
 Define your custom properties here.
 You can overwrite them through build.properties and
 ${user.home}/.build.properties
 ==========================================================
 --&gt;

 &lt;property name="myexec1" location="/usr/bin/myexec1"/&gt;
 &lt;property name="myexec2" location="/usr/bin/myexec2"/&gt;

&lt;/project&gt;
</code></pre>

Important thing here is to come up with as many useful default property values as possible, then you may even never come up with custom <code>build.properties</code> files.

Then you just <code>&lt;import&gt;</code> this file in your project's build.xml.

<pre><code>&lt;project
 name="my-project"
&gt;
 &lt;!-- this is done, so you may import my-project somewhere else --&gt;
 &lt;dirname
 property="my-project.basedir"
 file="${ant.file.my-project}"
 /&gt;

 &lt;import file="${my-project.basedir}/relative/path/to/properties.xml"/&gt;

 &lt;target name="using.myexec1"&gt;
 &lt;echo message="myexec1=${myexec1}"/&gt;
 &lt;/target&gt;
&lt;/project&gt;
</code></pre>

If you want a custom value for myexec1 in <code>my-project</code>, just drop a custom flat build.properties file in the same directory where build.xml is located.

The build.properties file may look like this:

<pre><code>myexec1=c:/custom/path/to/myexec1.exe
</code></pre>

blocks|key|1174299|text|我使用或多或少标准的build.properties和build-local.properties文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1174300|第一个变量包含所有环境通用的默认值，第二个变量仅包含异常。第一个签入subversion，而另一个没有签入。|1174301|编辑：复制/粘贴Akr的优秀想法|BOLD|1174302|此外，对于每个操作系统或其他可能部署构建系统的操作系统，您可能都有一个默认属性文件。这些文件也可以签入到您的版本控制系统中。|1174303|然后，Ant脚本将包含所有文件，如下所示(请记住:在Ant中，以第一个定义为准)：|1174304|<property+file="build-local.properties"/>
<property+file="build.properties"/>
<property+file="build-${os.name}.properties">|code-block|syntax|javascript|1174305|entityMap^0|A|G|R|M|0|0|0|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@$9|12|A|13|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|14|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|16|8|@]|D|@]|E|$R|S]]|$1|T|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|U|$]]

I use the more or less standard <code>build.properties</code> and <code>build-local.properties</code> files.

The first contains default values, common to all environments, the second only the exceptions. The first one is checked into subversion while the other is not.

EDIT : copy/pasting Akr's excellent idea

In addition you might have a default properties file for each of the OS or other you might deploy your build system on. These files can be checked in into your version control system as well.

The Ant script would then include all the files as follow (remember: in Ant the first definition wins):

<pre><code>&lt;property file="build-local.properties"/&gt;
&lt;property file="build.properties"/&gt;
&lt;property file="build-${os.name}.properties"&gt;
</code></pre>

blocks|key|1293193|text|除了Vladimir的解决方案之外，对于每个操作系统或其他可能部署构建系统的操作系统，您可能还有一个默认的属性文件。使用${os.name}+(和其他Java+system属性)设置路径。例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1293194|<property+file="build-${os.name}.properties">|code-block|syntax|javascript|1293195|这些文件也可以维护并签入到您的版本控制系统中。|1293196|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In addition to Vladimir's solution you might have a default properties file for each of the OS or other you might deploy your build system on. Use the ${os.name} (and other Java system properties) to set up a path. For example 

<pre><code>&lt;property file="build-${os.name}.properties"&gt;
</code></pre>

These files can be maintained and checked in into your version control system as well.

I have a number of file/executable locations that are likely to be different depending on which computer I am running them on, and I would like to abstract these out through ant properties somehow. What's the best way to do this? Is there a system-wide ant setup script that gets called? Or can I make such a script?

ant: best way to setup system-dependent properties?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有许多文件/可执行文件的位置，根据我在哪台计算机上运行它们，它们可能会有所不同，我想通过ant属性以某种方式将它们抽象出来。做这件事最好的方法是什么？是否有一个系统范围内的ant安装脚本会被调用？或者我可以写一个这样的脚本吗？

问ant:设置系统相关属性的最佳方式？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ant:设置系统相关属性的最佳方式？EN