blocks|key|292534|text|您可以使用java语法来完成此操作，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|292535|Properties+props+=+new+Properties()
InputStream+ins+=+new+FileInputStream("/path/file.properties")
props.load(ins)
ins.close()|code-block|syntax|javascript|292536|这应该可以在任何groovy脚本中工作。不过，可能还有一种更“时髦”的方法，使用闭包或其他一些奇特的快捷方式。|292537|编辑："+in“是groovy中的保留字。变量不能这样命名，请将其重命名为"ins“|292538|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You could do it using the java syntax, e.g.:

<pre><code>Properties props = new Properties()
InputStream ins = new FileInputStream("/path/file.properties")
props.load(ins)
ins.close()
</code></pre>

This should work in any groovy script. There might be a more "groovy" way of doing it though, using closures or some other fancy shortcut.

EDIT: "in" is a reserved word in groovy. A variable can't be named that way, renaming it to "ins"

blocks|key|292596|text|实际上，我推荐使用Gradle的默认属性文件。如果您将属性放在与build.gradle相同的目录下的gradle.properties中，则它们将自动可用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|292597|请参阅user+guide。|292598|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gradle.org/current/userguide/build_environment.html^0|W|C|1F|H|0|3|A|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

I would actually recommend using Gradle's default properties file. If you put the properties in <code>gradle.properties</code> in the same directory as the <code>build.gradle</code>, they will automatically be available.

See the <a href="https://docs.gradle.org/current/userguide/build_environment.html">user guide</a>.

blocks|key|292648|text|下面是我如何在我的.jar中包含Gradle构建的.csv文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|292649|sourceSets+{
++main+{
++++java+{
++++++srcDir+'src/main/java'
++++++output.classesDir+++=+'build/classes/main'++++++
++++}
++++resources+{
++++++srcDir+'src/main/resources'
++++++include+'*.csv'
++++++output.resourcesDir+=+'build/resources/main'
++++}
++}
}|code-block|syntax|javascript|292650|然后，当我的应用程序加载资源时，这是独立于Gradle完成的。|292651|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|$]]

Here is how I include a .csv file in my .jar that Gradle builds:

<pre><code>sourceSets {
 main {
 java {
 srcDir 'src/main/java'
 output.classesDir = 'build/classes/main' 
 }
 resources {
 srcDir 'src/main/resources'
 include '*.csv'
 output.resourcesDir = 'build/resources/main'
 }
 }
}
</code></pre>

Then, when my application loads the resource, that is done independently of Gradle.

blocks|key|509110|text|对于Gradle+1.x+(在Gradle+2.x中已弃用)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|509111|要包含您的.properties文件，您可以使用类似以下内容：|509112|++++apply+from:+"version.properties"|code-block|syntax|javascript|509113|就是这样！|509114|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<h2>For Gradle 1.x (deprecated in Gradle 2.x)</h2>
To include your .properties file you can just use something like this:
<pre><code> apply from: &quot;version.properties&quot;
</code></pre>
and that's it!

blocks|key|509151|text|您可能正在寻找的内容类似于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|509152|++++Properties+props+=+new+Properties()
++++props.load(new+FileInputStream("$project.rootDir/profile/"%2B"$environment"%2B".properties"))
++++props.each+{+prop+->
++++++project.ext.set(prop.key,+prop.value)
++++}|code-block|syntax|javascript|509153|然后，您的属性应该可以通过它们的名称直接访问。即：|509154|++println+"$jdbcURL"
++println+project.jdbcURL|509155|可能是有原因的(阴影？)为什么这么做是个坏主意？不确定为什么它不支持开箱即用或可以在其他地方找到。|509156|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

What you propably are looking for is something like:

<pre><code> Properties props = new Properties()
 props.load(new FileInputStream("$project.rootDir/profile/"+"$environment"+".properties"))
 props.each { prop -&gt;
 project.ext.set(prop.key, prop.value)
 }
</code></pre>

Your properties should then be accessible directly through their name.
I.e.:

<pre><code> println "$jdbcURL"
 println project.jdbcURL
</code></pre>

Theres probably a reason (shadowing?) why its a bad idea to do this? Not sure why its not supported out of the box or can be found somewhere else.

blocks|key|292823|text|我非常怀念Ant的这个特性，特别是像work.dir=${basedir}/work这样的内部替代特性。对于我使用的一些大型构建，执行大量环境设置以进行自动化测试，有些任务只需要用户和环境可配置设置。简单的"gradle.properties“是不够的，特别是对于跨多个项目共享的设置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|292824|我整理了一个示例gradle文件，它管理一个合理的属性加载方案：load-properties.gradle。这使项目可以精确地定义其在default-properties.gradle文件中使用的属性，并允许用户定义其本地设置以覆盖这些设置。因为读入的“属性”文件是gradle脚本，所以可以在其中包含额外的逻辑，并且值不仅限于字符串。|292825|此外，它允许通过向gradle传递"-Penv=(env+name)“参数来定义要使用的每个环境的属性文件(例如"mac”、"jenkins-machine“或"remote")。|292826|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/groboclown/a5cf5622641b2251d18adbe5561015f1^0|I|O|0|1W|P|W|M|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

I have been sorely missing this feature of Ant, especially the in-property replacement like <code>work.dir=${basedir}/work</code>. With some of the large builds I work with that perform lots of environment setup for automated tests, there are some tasks that just need user and environment configurable settings. The simple "gradle.properties" just isn't enough, especially for settings that are shared across multiple projects.

I put together an example gradle file that manages a reasonable property loading scheme: <a href="https://gist.github.com/groboclown/a5cf5622641b2251d18adbe5561015f1" rel="nofollow">load-properties.gradle</a>. This lets the project define exactly the properties it uses in a <code>default-properties.gradle</code> file, and allows users to define their local settings to override them. Because the "property" files read in are gradle scripts, you can include extra logic in them, and the values aren't limited to just strings.

Additionally, it allows for defining a per-environment properties file to use (such as "mac", or "jenkins-machine", or "remote") by passing in a "-Penv=(env name)" parameter to gradle.

blocks|key|509414|text|被接受的答案是有效的，除非你想将属性添加到项目中，因为这是第一个搜索结果，所以我将添加我的解决方案，它在gradle+3.x中有效。一种简单的方法是通过ant。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|509415|ant+{
++++property(file:+'properties.file')
}|code-block|syntax|javascript|509416|如果您需要将属性转换为驼峰大小写以便在脚本中轻松访问(请记住基于点的语法期望和实际对象存在于gradle中)：|509417|println+"property+value:{dot.property.from.file}"+//this+will+fail.
def+camelCaseProperty+=+project.getProperties().get("dot.property.from.file")
println+"camelCaseProperty:${camelCaseProperty}"++//this+wont+fail|509418|如果在未指定的情况下需要默认值：|509419|def+propertyWithDefault+=+project.getProperties().get("dot.property.from.file","defaultValue");|509420|通过使用这种方法，至少在IntelliJ/Android+Studio中，IDE将链接您的属性文件和gradle脚本，并添加完成、引用检查等功能。|509421|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

The accepted answer works unless you want to add the properties to the project, since this is the first search result I'll add my solution which works in gradle 3.x. An easy way to do it is through ant.

<pre><code>ant {
 property(file: 'properties.file')
}
</code></pre>

If you need to convert the property to Camel Case for easy access in your script (remember dot based syntax expects and actual object to exist in gradle):

<pre><code>println "property value:{dot.property.from.file}" //this will fail.
def camelCaseProperty = project.getProperties().get("dot.property.from.file")
println "camelCaseProperty:${camelCaseProperty}" //this wont fail
</code></pre>

If you need a default value if it's not specified:

<pre><code>def propertyWithDefault = project.getProperties().get("dot.property.from.file","defaultValue");
</code></pre>

By using this method, at least with IntelliJ/Android Studio, the IDE will link your properties file and gradle script and add completion, reference checking, etc.

blocks|key|293011|text|在您的任务(jar或任何其他任务)中，可以通过这种方式将任何文件包含到目标文件夹中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|293012|jar{

++++//jar+task+related+code

+++from("src/main/......(source)")+{+
+++++include+'xxx.properties'+into('com/.....(destination)')+

+++}

}|code-block|syntax|javascript|293013|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In your task (jar or any other task) you can do this way to include any file into the destination folder

<pre><code>jar{

 //jar task related code

 from("src/main/......(source)") { 
 include 'xxx.properties' into('com/.....(destination)') 

 }

}
</code></pre>

How would I include a properties file in Gradle?

For example in Ant, I could do the following:

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

Gradle - Include Properties File

Android Studio

Android

如何在Gradle中包含属性文件？例如，在Ant中，我可以执行以下操作：<property file="${basedir}/build.properties" />

问Gradle -包含属性文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle -包含属性文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle -包含属性文件
EN