blocks|key|181882|text|buildScript块确定哪些插件、任务类和其他类可用于构建脚本的其余部分。如果没有buildScript块，您可以使用Gradle附带的一切开箱即用。如果您还想使用第三方插件、任务类或其他类(在构建脚本中！)，则必须在buildScript块中指定相应的依赖项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|181883|entityMap^0|0|B|17|B|33|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

The <code>buildScript</code> block determines which plugins, task classes, and other classes are available for use in the rest of the build script. Without a <code>buildScript</code> block, you can use everything that ships with Gradle out-of-the-box. If you additionally want to use third-party plugins, task classes, or other classes (in the build script!), you have to specify the corresponding dependencies in the <code>buildScript</code> block.

blocks|key|2795406|text|我很欣赏Peter的回答。但对于我来说，答案和文档中强调的构建脚本的其余部分的含义并不是很明显。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2795407|通常，引入依赖功能是为了在Java程序或您可能正在编写的任何其他程序中使用。引入Spring+say，不是在构建脚本中使用，而是在Java程序中使用。将其放入buildscript闭包中可确保依赖项可在gradle构建本身中使用。而不是输出程序。|offset|length|style|CODE|2795408|entityMap^0|0|27|B|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I appreciate Peter's answer... but it was not immediately obvious to me what the rest of the build script meant as emphasized in the answer and in the documentation.

Usually bringing in dependent functionality is for use in the Java program or whatever other program you might be writing. Bringing in Spring say, is not to be used in the build script, but in the Java program. Putting it in the <code>buildscript</code> closure ensures that the dependencies are available for use within the gradle build itself. Not the output program.

blocks|key|2795431|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2795432|全局级别的dependencies和repositories部分列出了构建源代码和运行源代码等所需的依赖项。|unordered-list-item|offset|length|style|CODE|2795433|+buildscript用于build.gradle文件本身。因此，这将包含用于创建build.gradle|2795434|、Dockerfile的依赖项，以及用于在所有依赖RPM中运行任务的任何其他依赖项|2795435|entityMap^0|0|5|C|I|C|0|1|B|E|C|16|C|0|1|A|0^^$0|@$1|2|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|O|7|@$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|8|@]|9|$]]|$1|H|3|I|4|C|6|T|7|@$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|8|@]|9|$]]|$1|J|3|K|4|5|6|10|7|@$D|11|E|12|F|G]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|13|7|@]|8|@]|9|$]]]|M|$]]

<ul>
<li>The global level <code>dependencies</code> and <code>repositories</code> sections list dependencies that required for building your source and running your source etc.</li>
<li>The <code>buildscript</code> is for the <code>build.gradle</code> file itself. So, this would contain dependencies for say creating RPMs, <code>Dockerfile</code>, and any other dependencies for running the tasks in all the dependent <code>build.gradle</code></li>
</ul>

blocks|key|3007987|text|"buildscript“配置部分是针对gradle本身的(即更改gradle执行构建的方式)。因此，这一部分通常包括Android+Gradle插件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3007988|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The "buildscript" configuration section is for gradle itself (i.e. changes to how gradle is able to perform the build). So this section will usually include the Android Gradle plugin.

blocks|key|3008016|text|这是一个有点高的水平，但希望有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3008017|对我来说，一旦我开始理解什么是a+building+block、方法和任务，就开始形成清晰的区别。语法是什么样子，你如何配置它们等等。所以我建议你把所有这些都看一遍。在此之后，您可以开始理解此语法。|offset|length|3008018|然后非常重要的是要知道什么是对象项目(+build.gradle类的一个实例)的类型，以便知道在build.gradle文件中可以有什么。这就回答了“buildScript”和其他词从何而来。为了扩展你的能力/特性(比如说安卓)，看看plugins是如何帮助你的。|3008019|最后但并非最不重要的是，这里有一个非常好的tutorial，它讨论了闭包，委托，这是理解脚本所必需的概念。|3008020|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gradle.org/current/dsl/index.html|1|https://google.github.io/android-gradle-dsl/current/|2|https://www.youtube.com/watch?v=9S4AgFZsxcQ&t=1531s^0|0|F|G|0|0|39|7|1|0|L|8|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]|T|$5|M|N|O|A|$P|U]]]]

It's a bit high level but hope helps.

For me, clear distinction started to shape once I start to understand what is <a href="https://docs.gradle.org/current/dsl/index.html" rel="nofollow noreferrer">a building block</a>, method, and task. How the syntax looks like, how you can configure them etc. So I suggest you go through all these. After that, you can begin to make sense out of this syntax. 

Then it's very important to know what's the type of the object build.gradle (an instance of Project class) so to know what can you have inside a build.gradle file. That would answer where that 'buildScript' and others come from. And to extend your capabilities/features (let's say android), see how <a href="https://google.github.io/android-gradle-dsl/current/" rel="nofollow noreferrer">plugins</a> can help.

Last but not least, there's a very good <a href="https://www.youtube.com/watch?v=9S4AgFZsxcQ&amp;t=1531s" rel="nofollow noreferrer">tutorial</a> here that talks about closures, delegates which are the concepts essential to understand the script.

blocks|key|3008033|text|通过演示Android顶级gradle文件来进行更多的解释。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3008034|buildscript+{
++++//+this+is+where+we+are+going+to+find+the+libraries+defined+in+"dependencies+block"+at+below
++++repositories+{
++++++++google()
++++++++jcenter()
++++++++maven+{+url+'https://dl.bintray.com/kotlin/kotlin-eap'+}
++++}

++++//+everything+listed+in+the+dependencies+is+actually+a+plugin,+which+we'll+do+"apply+plugin"+in+our+module+level+gradle+file.
++++dependencies+{
++++++++classpath+'com.android.tools.build:gradle:3.4.2'+//+this+is+android+gradle+plugin
++++++++classpath+"org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"+//+kotlin+gradle+plugin
++++}
}|code-block|syntax|javascript|3008035|模块级gradle文件|3008036|apply+plugin:+'com.android.application'
apply+plugin:+'kotlin-android'
apply+plugin:+'kotlin-android-extensions'|3008037|什么是"plugin"？它们只是实现插件接口的java类。在接口下，有一个方法"apply“，可以添加多个不同名称的任务对象。Task是一个类，我们可以在其中实现工作流。例如，构建任务由构建应用程序的流程组成。|3008038|那么，buildscript做些什么呢？它定义了哪里可以找到插件。插件是做什么的？它包含多个任务。任务是做什么的？它为我们提供了构建、安装、lint等。|3008039|我的理解可能是错误的。如果你发现任何误导性的东西，请不要犹豫，请纠正我。|3008040|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|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

A bit more explanation by demonstrating Android top-level gradle file. 

<pre><code>buildscript {
 // this is where we are going to find the libraries defined in "dependencies block" at below
 repositories {
 google()
 jcenter()
 maven { url 'https://dl.bintray.com/kotlin/kotlin-eap' }
 }

 // everything listed in the dependencies is actually a plugin, which we'll do "apply plugin" in our module level gradle file.
 dependencies {
 classpath 'com.android.tools.build:gradle:3.4.2' // this is android gradle plugin
 classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version" // kotlin gradle plugin
 }
}
</code></pre>

module level gradle file

<pre><code>apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'
</code></pre>

What is "plugin"? They are just java classes, which implement Plugin interface. Under the interface, it has a method "apply" to add multiple task objects with different names. Task is a class where we can implement the workflow. For instance, the build task consists of the flow of building the app.

So, what does buildscript do? It defines where to find the plugins. What does plugin do? It encompasses multiple tasks. What does task do? It provides us with the build, install, lint, etc. 

My understanding might be wrong. Please don't hesitate to correct me if you find anything is misleading.

blocks|key|3008059|text|gradle块用于构建脚本，而不是buildscript构建输出(例如，Android应用程序apk)。在下面的代码示例中，编码代码在构建脚本中使用，而不是在gradle构建输出程序中使用；因此依赖项应该添加到buildscript块中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3008060|https://docs.gradle.org/current/userguide/tutorial_using_tasks.html#sec:build_script_external_dependencies|3008061|构建脚本的|3008062|+外部依赖项|blockquote|BOLD|3008063|3008064|建议应用带有自己的类路径的插件，而不是直接操作脚本类路径。对于自定义构建逻辑，建议使用自定义插件。如果生成脚本需要使用外部库，则可以将它们添加到生成脚本本身的脚本类路径中。您可以使用buildscript()方法，传入一个声明构建脚本类路径的块。|3008065|传递给buildscript()方法的块配置一个ScriptHandler实例。您可以通过向类路径配置添加依赖项来声明构建脚本类路径。这与声明Java编译类路径的方式相同。您可以使用除项目依赖项之外的任何依赖项类型。|3008066|声明了构建脚本类路径之后，您可以在构建脚本中使用这些类，就像使用类路径上的任何其他类一样。下面的示例添加到前面的示例中，并使用生成脚本类路径中的类。|3008067|3008068|import+org.apache.commons.codec.binary.Base64

buildscript+{
++++repositories+{
++++++++mavenCentral()
++++}
++++dependencies+{
++++++++classpath+group:+'commons-codec',+name:+'commons-codec',+version:+'1.2'
++++}
}

tasks.register('encode')+{
++++doLast+{
++++++++def+byte[]+encodedString+=+new+Base64().encode('hello+world\n'.getBytes())
++++++++println+new+String(encodedString)
++++}
}|code-block|syntax|javascript|3008069|entityMap|0|LINK|mutability|MUTABLE|url^0|H|B|2X|B|0|0|2Y|0|0|0|1|5|0|0|0|3F|0|0|30|0|0|22|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|H|3|I|5|6|7|1G|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1H|8|@$9|1I|A|1J|B|M]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1L|8|@$9|1M|A|1N|B|M]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1O|8|@$9|1P|A|1Q|B|M]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1R|8|@$9|1S|A|1T|B|M]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]|$1|V|3|W|5|X|7|1V|8|@]|D|@]|E|$Y|Z]]|$1|10|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|G]]]]

<code>buildscript</code> block is used for the build script, NOT for the gradle build output (for example, an Android app apk). In the following code example, the encoding code is used in build script, not in the gradle build output program; so the dependecies should be added to <code>buildscript</code> block.
<a href="https://docs.gradle.org/current/userguide/tutorial_using_tasks.html#sec:build_script_external_dependencies" rel="nofollow noreferrer">https://docs.gradle.org/current/userguide/tutorial_using_tasks.html#sec:build_script_external_dependencies</a>
<blockquote>
External dependencies for the build script
Instead of manipulating the
script classpath directly, it is recommended to apply plugins that
come with their own classpath. For custom build logic, the
recommendation is to use a custom plugin. If your build script needs
to use external libraries, you can add them to the script’s classpath
in the build script itself. You do this using the buildscript()
method, passing in a block which declares the build script classpath.
The block passed to the buildscript() method configures a ScriptHandler instance.
You declare the build script classpath by adding dependencies to the
classpath configuration. This is the same way you declare, for
example, the Java compilation classpath. You can use any of the
dependency types except project dependencies.
Having declared the build script classpath, you can use the classes in
your build script as you would any other classes on the classpath. The
following example adds to the previous example, and uses classes from
the build script classpath.
</blockquote>
<pre><code>import org.apache.commons.codec.binary.Base64

buildscript {
 repositories {
 mavenCentral()
 }
 dependencies {
 classpath group: 'commons-codec', name: 'commons-codec', version: '1.2'
 }
}

tasks.register('encode') {
 doLast {
 def byte[] encodedString = new Base64().encode('hello world\n'.getBytes())
 println new String(encodedString)
 }
}
</code></pre>

I am new to Gradle and I am reading the documentation but I don't understand some parts of it. One of these parts is connected with <code>buildscript</code> block. What is its purpose?



<blockquote>
 If your build script needs to use external libraries, you can add them to the script's classpath in the build script itself. You do this using the buildscript() method, passing in a closure which declares the build script classpath.

<pre class="lang-groovy prettyprint-override"><code>buildscript {
 repositories {
 mavenCentral()
 }
 dependencies {
 classpath group: 'commons-codec', name: 'commons-codec', version: '1.2'
 }
}
</code></pre>
</blockquote>

Ok but what is the difference with:

<pre class="lang-groovy prettyprint-override"><code>repositories {
 mavenCentral()
}
dependencies {
 compile group: 'commons-codec', name: 'commons-codec', version: '1.2'
}
</code></pre>

For example, why it is necessary to use <code>buildscript</code>?

Purpose of buildscript block in Gradle

我是Gradle的新手，我正在阅读文档，但我不了解其中的某些部分。其中一个部件与buildscript模块相连。它的目的是什么？如果生成脚本需要使用外部库，则可以将它们添加到生成脚本本身的脚本类路径中。您可以使用buildscript()方法，传入一个闭包来声明构建脚本类路径。buildscript {存储库{ mav...

问Gradle中buildscript块的用途
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle中buildscript块的用途EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle中buildscript块的用途
EN