0

根据此页面: https ://docs.gradle.org/current/samples/sample_building_kotlin_applications.html#run_the_init_task runninggradle init会给我一个选项列表。

不,它没有;它只是说“构建成功”并构建没有应用程序目录的目录结构。

我想我应该在某处设置一些默认的东西。在我不知道如何称呼这些东西之前没有使用过 gradle,所以我可以搜索它们,也不知道它们应该去哪里的名称。有谁知道把东西放在某个地方的说明在哪里?如果你能回答这个问题,你可能认识可能会改进文档的人——这样可以避免你回答像这样的愚蠢问题 :-)

响应下面的请求,这是使用 -i 的完整输出:

pi@dadsDesktop:~/tmpry/demo $ gradle -i init
Initialized native services in: /home/pi/.gradle/native
The client will now receive all logging from the daemon (pid: 27866). The daemon log file: /home/pi/.gradle/daemon/4.4.1/daemon-27866.out.log
Starting 2nd build in daemon [uptime: 1 mins 43.436 secs, performance: 98%]
Using 4 worker leases.
Creating new cache for fileHashes, path /home/pi/tmpry/demo/.gradle/4.4.1/fileHashes/fileHashes.bin, access org.gradle.cache.internal.DefaultCacheAccess@358daf
Starting Build
Settings evaluated using settings file '/home/pi/tmpry/demo/settings.gradle'.
Projects loaded. Root project using build file '/home/pi/tmpry/demo/build.gradle'.
Included projects: [root project 'demo']

> Configure project : 
Evaluating root project 'demo' using build file '/home/pi/tmpry/demo/build.gradle'.

All projects evaluated.
Selected primary task 'init' from project :
Tasks to be executed: [task ':wrapper', task ':init']
Creating new cache for resourceHashesCache, path /home/pi/tmpry/demo/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access org.gradle.cache.internal.DefaultCacheAccess@358daf
Creating new cache for taskHistory, path /home/pi/tmpry/demo/.gradle/4.4.1/taskHistory/taskHistory.bin, access org.gradle.cache.internal.DefaultCacheAccess@b60cd6
Creating new cache for outputFiles, path /home/pi/tmpry/demo/.gradle/buildOutputCleanup/outputFiles.bin, access org.gradle.cache.internal.DefaultCacheAccess@179e5c6
:wrapper (Thread[Daemon worker Thread 2,5,main]) started.

> Task :wrapper 
Putting task artifact state for task ':wrapper' into context took 0.0 secs.
Up-to-date check for task ':wrapper' took 0.009 secs. It is not up-to-date because:
  No history is available.

:wrapper (Thread[Daemon worker Thread 2,5,main]) completed. Took 0.32 secs.
:init (Thread[Daemon worker Thread 2,5,main]) started.

> Task :init 
Putting task artifact state for task ':init' into context took 0.0 secs.
Up-to-date check for task ':init' took 0.0 secs. It is not up-to-date because:
  Task has not declared any outputs.

:init (Thread[Daemon worker Thread 2,5,main]) completed. Took 0.114 secs.

BUILD SUCCESSFUL in 2s
2 actionable tasks: 2 executed
4

1 回答 1

0

答案是,对于旧版本的 gradle(例如您apt-get install gradle在 2020 年 11 月左右获得的树莓派版本),您需要使用该选项指定要生成的事物的类型 --type,以及项目的结构(?) . 在我的情况下--dsl kotlin

这些属性在“插件”下的文档中指定。只是对于那些认为这很明显的人,指定这些元素的另一种方法是在 gradle 可以自己解决的上下文(无论是什么)中运行它。这显然是它的正常使用方式。不幸的是,我可用的上下文( kotlin/gradle/inteliJ )在 pi 上不起作用。使用make并不容易,但我怀疑并不难,而且我敢打赌make更稳定:-/

于 2020-11-18T11:46:56.257 回答