blocks|key|4535190|text|要进行离线构建，您需要以某种方式提供所有必需的依赖项。这里的一个选项就是将这些jars提交到版本控制中。困难的部分是收集所有这些依赖项。为此，可以有一个可以在两种模式(在线和离线)下操作的build.gradle文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4535191|buildscript+{
++++repositories+{
++++++++if+('allow'+==+System.properties['build.network_access'])+{
++++++++++++mavenCentral()
++++++++}+else+{
++++++++++++maven+{
++++++++++++++++url+'dependencies'
++++++++++++}
++++++++}
++++}
++++dependencies+{
++++++++classpath+'com.android.tools.build:gradle:1.2.0-beta2'
++++}
}|code-block|syntax|javascript|4535192|要在脱机模式下运行，请键入以下内容：|4535193|gradle+--offline|4535194|并在联机模式下运行：|4535195|gradle+-Dbuild.network_access=allow|4535196|要收集所有依赖项，请使用将在联机模式下运行gradle的脚本，将依赖项提取到${project_dir}/.gradle_home中的缓存中，并将工件复制到dependencies文件夹中的本地maven存储库。|offset|length|style|CODE|4535197|#!/usr/bin/python

import+sys
import+os
import+subprocess
import+glob
import+shutil

#+Place+this+in+build.gradle:
#+repositories+{
#+++++if+('allow'+==+System.properties['build.network_access'])+{
#+++++++++mavenCentral()
#+++++}+else+{
#+++++++++maven+{+url+'dependencies'+}
#+++++}
#+}
def+main(argv):
++++project_dir+=+os.path.dirname(os.path.realpath(__file__))
++++repo_dir+=+os.path.join(project_dir,+"dependencies")
++++temp_home+=+os.path.join(project_dir,+".gradle_home")
++++if+not+os.path.isdir(temp_home):
++++++++os.makedirs(temp_home)
++++subprocess.call(["gradle",+"-g",+temp_home,+"-Dbuild.network_access=allow"])
++++cache_files+=+os.path.join(temp_home,+"caches/modules-*/files-*")
++++for+cache_dir+in+glob.glob(cache_files):
++++++++for+cache_group_id+in+os.listdir(cache_dir):
++++++++++++cache_group_dir+=+os.path.join(cache_dir,+cache_group_id)
++++++++++++repo_group_dir+=+os.path.join(repo_dir,+cache_group_id.replace('.',+'/'))
++++++++++++for+cache_artifact_id+in+os.listdir(cache_group_dir):
++++++++++++++++cache_artifact_dir+=+os.path.join(cache_group_dir,+cache_artifact_id)
++++++++++++++++repo_artifact_dir+=+os.path.join(repo_group_dir,+cache_artifact_id)
++++++++++++++++for+cache_version_id+in+os.listdir(cache_artifact_dir):
++++++++++++++++++++cache_version_dir+=+os.path.join(cache_artifact_dir,+cache_version_id)
++++++++++++++++++++repo_version_dir+=+os.path.join(repo_artifact_dir,+cache_version_id)
++++++++++++++++++++if+not+os.path.isdir(repo_version_dir):
++++++++++++++++++++++++os.makedirs(repo_version_dir)
++++++++++++++++++++cache_items+=+os.path.join(cache_version_dir,+"*/*")
++++++++++++++++++++for+cache_item+in+glob.glob(cache_items):
++++++++++++++++++++++++cache_item_name+=+os.path.basename(cache_item)
++++++++++++++++++++++++repo_item_path+=+os.path.join(repo_version_dir,+cache_item_name)
++++++++++++++++++++++++print+"%25s:%25s:%25s+(%25s)"+%25+(cache_group_id,+cache_artifact_id,+cache_version_id,+cache_item_name)
++++++++++++++++++++++++shutil.copyfile(cache_item,+repo_item_path)
++++shutil.rmtree(temp_home)
++++return+0

if+__name__+==+"__main__":
++++sys.exit(main(sys.argv))|4535198|因此，每次更改依赖项后，只需运行此脚本并将更改提交到dependencies文件夹。然后，您可以使用gradle+--offline或仅使用gradle离线构建。|4535199|entityMap^0|0|0|0|0|0|0|12|R|26|C|0|0|Q|C|1E|G|1Y|6|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@$Q|17|R|18|S|T]|$Q|19|R|1A|S|T]]|9|@]|A|$]]|$1|U|3|V|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1C|8|@$Q|1D|R|1E|S|T]|$Q|1F|R|1G|S|T]|$Q|1H|R|1I|S|T]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$]]

To have an offline build you need somehow to provide all required dependencies. One of the options here is just to commit those jars into version control. The hard part is to collect all those dependencies. For that it's possible to have a build.gradle file that can operate in two modes (online and offline):

<pre class="lang-groovy prettyprint-override"><code>buildscript {
 repositories {
 if ('allow' == System.properties['build.network_access']) {
 mavenCentral()
 } else {
 maven {
 url 'dependencies'
 }
 }
 }
 dependencies {
 classpath 'com.android.tools.build:gradle:1.2.0-beta2'
 }
}
</code></pre>

To run in offline mode type:

<pre><code>gradle --offline
</code></pre>

And to run in online mode:

<pre><code>gradle -Dbuild.network_access=allow
</code></pre>

And to collect all dependencies use this script that will run gradle in online mode, fetch dependencies to cache inside <code>${project_dir}/.gradle_home</code> and copy artifacts to local maven repository in <code>dependencies</code> folder.

<pre class="lang-python prettyprint-override"><code>#!/usr/bin/python

import sys
import os
import subprocess
import glob
import shutil

# Place this in build.gradle:
# repositories {
# if ('allow' == System.properties['build.network_access']) {
# mavenCentral()
# } else {
# maven { url 'dependencies' }
# }
# }
def main(argv):
 project_dir = os.path.dirname(os.path.realpath(__file__))
 repo_dir = os.path.join(project_dir, "dependencies")
 temp_home = os.path.join(project_dir, ".gradle_home")
 if not os.path.isdir(temp_home):
 os.makedirs(temp_home)
 subprocess.call(["gradle", "-g", temp_home, "-Dbuild.network_access=allow"])
 cache_files = os.path.join(temp_home, "caches/modules-*/files-*")
 for cache_dir in glob.glob(cache_files):
 for cache_group_id in os.listdir(cache_dir):
 cache_group_dir = os.path.join(cache_dir, cache_group_id)
 repo_group_dir = os.path.join(repo_dir, cache_group_id.replace('.', '/'))
 for cache_artifact_id in os.listdir(cache_group_dir):
 cache_artifact_dir = os.path.join(cache_group_dir, cache_artifact_id)
 repo_artifact_dir = os.path.join(repo_group_dir, cache_artifact_id)
 for cache_version_id in os.listdir(cache_artifact_dir):
 cache_version_dir = os.path.join(cache_artifact_dir, cache_version_id)
 repo_version_dir = os.path.join(repo_artifact_dir, cache_version_id)
 if not os.path.isdir(repo_version_dir):
 os.makedirs(repo_version_dir)
 cache_items = os.path.join(cache_version_dir, "*/*")
 for cache_item in glob.glob(cache_items):
 cache_item_name = os.path.basename(cache_item)
 repo_item_path = os.path.join(repo_version_dir, cache_item_name)
 print "%s:%s:%s (%s)" % (cache_group_id, cache_artifact_id, cache_version_id, cache_item_name)
 shutil.copyfile(cache_item, repo_item_path)
 shutil.rmtree(temp_home)
 return 0

if __name__ == "__main__":
 sys.exit(main(sys.argv))
</code></pre>

So, after each dependency change just run this script and commit changes in <code>dependencies</code> folder. Then you can build offline with <code>gradle --offline</code> or just <code>gradle</code>.

blocks|key|4535230|text|在过去，我使用了类似的解决方案，尽管“我的”复制脚本是用groovy而不是python完成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4535231|几周前，我发现了另一种方法：ivypot+plugin。现在你不再需要使用任何“外部”脚本，这个插件能够将所有依赖项复制到一个常春藤存储库的本地目录中。|offset|length|4535232|可以在on+github中找到测试项目。我可以提供一个英文自述文件的情况下有它的需求。|4535233|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ysb33r/ivypot-gradle-plugin|1|https://github.com/uli-heller/uli-gradle/tree/master/053-local-repository^0|0|E|D|0|0|3|9|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

In the past, I used a similar solution, though "my" copy script was done in groovy instead of python.

I detected another approach a couple of weeks ago: There is the <a href="https://github.com/ysb33r/ivypot-gradle-plugin" rel="noreferrer">ivypot plugin</a>. Now you don't have to use any "external" script any more, the plugin is able to copy all dependencies into a local directory which is an ivy repo.

A test project can be found <a href="https://github.com/uli-heller/uli-gradle/tree/master/053-local-repository" rel="noreferrer">on github</a>. I can provide an English README in case there is demand for it.

I am working on implementing a Gradle build system for a piece of software that has parts that are developed in area without Internet connectivity or the ability to install a Maven/Ivy server (like Nexus). To support development in these environments, I am putting together a Gradle plugin that allows the generation of an "Offline Workspace".

I originally implemented this functionality by triggering the resolution of each configuration in the project (triggering the download of all dependencies), then traversing the entire dependency tree of each configuration and copying the local cached copy of the dependency into the Offline Workspace. (A Copy task was generated for each copy operation.) These JARs would then be referenced using a flatDir repository.

This implementation performed its job using an afterEvaluate block. While this worked fine in Gradle 2.0, it triggers a deprecation warning in Gradle 2.2.1 because triggering the resolution is somehow seen as modifying a configuration after it has already been resolved (<code>Attempting to change configuration ':core:runtime' after it has been included in dependency resolution. This behaviour has been deprecated and is scheduled to be removed in Gradle 3.0</code>). In all, this approach feels rather hacky since it also requires me to modify the build.gradle files to explicitly list all transitive dependencies since there are no POM files available to properly specify dependencies.

A more elegant approach seems like it would build a local Maven repository of all dependencies (including POM files, source JARs, javadoc JARs, etc) and then just use the mavenLocal() repository type. Unfortunately, I'm not sure how to do this properly where I don't need to trigger artifact resolution in order to perform this operation.

Is there some better way that I can achieve the full artifact download into an easy-to-package way than just zipping up my entire $USER_HOME/.gradle directory?

Build Gradle repository for offline development

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在为一个软件实现Gradle构建系统，该软件的某些部分是在没有Internet连接或无法安装Maven/Ivy服务器(如Nexus)的区域开发的。为了支持这些环境中的开发，我正在组装一个Gradle插件，它允许生成一个“离线工作区”。我最初实现此功能的方式是触发项目中每个配置的解析(触发所有依赖项的下载)，然后遍历...

问为离线开发构建Gradle存储库
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为离线开发构建Gradle存储库EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为离线开发构建Gradle存储库
EN