当前位置: 首页 > 知识库问答 >
问题:

execcommand==null!构建intellij idea插件时

查宜民
2023-03-14

当我试图在gradle中构建“Run IDE”配置文件时,我得到了以下错误

在http://www.jetbrains.org/intellij/sdk/docs/tutorials/build_system/prestiisites.html运行本教程

08:18:04.614 [ERROR]
[org.gradle.internal.buildevents.BuildExceptionReporter] 
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Execution failed for task ':runIde'.
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > execCommand == null!
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try:
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Run with --stacktrace option to get the stack trace. 
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] 
08:18:04.614 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 26s
08:18:04.614 [LIFECYCLE] [org.gradle.internal.buildevents.BuildResultLogger] 8 actionable tasks: 2 executed, 6 up-to-date
08:18:04.614 [DEBUG] [org.gradle.internal.work.DefaultWorkerLeaseService] Worker lease root.1 completed (0 worker(s) in use)
08:18:04.614 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker: released lock on root.1
08:18:04.614 [DEBUG] [org.gradle.internal.progress.DefaultBuildOperationExecutor] Completing Build operation 'Run build'
08:18:04.614 [DEBUG] [org.gradle.launcher.daemon.server.SynchronizedDispatchConnection] thread 19: dispatching class org.gradle.launcher.daemon.protocol.BuildEvent
08:18:04.614 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file content cache (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileContent)
08:18:04.614 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache annotation-processors.bin (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileContent\annotation-processors.bin)
08:18:04.614 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on file content cache (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileContent).
08:18:04.630 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for task history cache (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\taskHistory)
08:18:04.630 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache taskHistory.bin (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\taskHistory\taskHistory.bin)
08:18:04.630 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache fileSnapshots.bin (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\taskHistory\fileSnapshots.bin)
08:18:04.630 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on task history cache (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\taskHistory).
08:18:04.646 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 2, disk reads: 1 (avg: 0.004 secs, total: 0.004 secs)
08:18:04.646 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 0 (avg: 0.0 secs, total: 0.0 secs)
08:18:04.661 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.ResolutionResultsStoreFactory] Deleted 4 resolution results binary files in 0.014 secs
08:18:04.661 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Plugin Resolution Cache (C:\Users\saisr\.gradle\caches\4.0\plugin-resolution)
08:18:04.661 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache plugin-use-metadata.bin (C:\Users\saisr\.gradle\caches\4.0\plugin-resolution\plugin-use-metadata.bin)
08:18:04.661 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Plugin Resolution Cache (C:\Users\saisr\.gradle\caches\4.0\plugin-resolution).
08:18:04.661 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Artifact transforms cache (C:\Users\saisr\.gradle\caches\transforms-1)
08:18:04.661 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Artifact transforms cache (C:\Users\saisr\.gradle\caches\transforms-1).
08:18:04.661 [DEBUG] [org.gradle.workers.internal.WorkerDaemonFactory] Stopping 0 worker daemon(s).
08:18:04.661 [INFO] [org.gradle.workers.internal.WorkerDaemonFactory] Stopped 0 worker daemon(s).
08:18:04.661 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file hash cache (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileHashes)
08:18:04.661 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache fileHashes.bin (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileHashes\fileHashes.bin)
08:18:04.661 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache resourceHashesCache.bin (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileHashes\resourceHashesCache.bin)
08:18:04.661 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on file hash cache (C:\Users\saisr\IdeaProjects\mvn-refresher\.gradle\4.0\fileHashes).
08:18:04.677 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopping 0 deployment handles
08:18:04.677 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopped deployment handles
08:18:04.677 [DEBUG] [org.gradle.cache.internal.DefaultCacheAccess] Cache Generated Gradle JARs cache (C:\Users\saisr\.gradle\caches\4.0\generated-gradle-jars) was closed 0 times.
08:18:04.677 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for artifact cache (C:\Users\saisr\.gradle\caches\modules-2)
08:18:04.677 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache artifact-at-repository.bin (C:\Users\saisr\.gradle\caches\modules-2\metadata-2.23\artifact-at-repository.bin)
08:18:04.677 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache module-metadata.bin (C:\Users\saisr\.gradle\caches\modules-2\metadata-2.23\module-metadata.bin)
08:18:04.677 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache module-artifacts.bin (C:\Users\saisr\.gradle\caches\modules-2\metadata-2.23\module-artifacts.bin)
08:18:04.677 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on artifact cache (C:\Users\saisr\.gradle\caches\modules-2).
08:18:04.677 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has finished executing the build.
Cause: execCommand == null!
8:18:04 AM: Task execution finished 'runIde --debug'.

共有1个答案

鲁俊友
2023-03-14

我想这是gradle-intellij-plugin的一个bug,请看这个问题。我在build.gradle中将org.jetbrains.intellij的版本从0.3.0升级到0.3.4,并解决了这个问题。

 类似资料:
  • 问题内容: 我的詹金斯号建筑刚开始失败,并显示以下消息: 这是怎么回事? 问题答案: 对于那些对 “为什么” 感兴趣的人 ,我做了更多的挖掘工作,看来正在发生的事情是这样的: RunnerBootstrapper尝试检查版本是否为5.2+: 首先,从在EmbeddedRunner中创建的启动器检索 serverVersion , 使用IsolatedLauncher创建代理的实现类BatchIso

  • 问题内容: 是否有一个插件可以让我为hudson构建创建一个“趋势”图,从而显示该项目的构建时间? 我的任务是加快构建速度,并希望在加快速度时显示出不错的趋势。 问题答案: 开箱即用地支持此功能:http:// SERVER / hudson / job / JOBNAME / buildTimeTrend

  • 下面的这些代码可以帮助您通过CSS文件和SCSS文件,创建和编译 CSS 和 JS 文件的source-maps。 安装依赖 为了运行编译和压缩任务,你必须安装 node 和 npm。 命令行 // (Optional) Install Gulp module globally npm install gulp -g // Install fullpage's build dependen

  • Spring Boot为Maven和Gradle提供构建工具插件。 这些插件提供了各种功能,包括可执行jar的包装。 本节提供了有关这两个插件的更多详细信息,以及在需要扩展不受支持的构建系统时的一些帮助。

  • 如果作业使用构建流(包括重复作业)运行,构建管道插件是否仍然正确显示作业序列? 以下是构建流程的伪代码: 包将从源代码控制中提取代码,编译它,并将其存储为工件 部署将从上游Package作业复制工件,然后将其复制到目标参数中提供的URL 集成测试将针对参数中提供的URL运行一套集成测试。 即使部署作业重复,构建管道插件是否将此管道显示为4个步骤?

  • 问题内容: 是否有任何Gradle教程或插件显示如何借助Gradle构建来构建/分发Eclipse插件? Somethig类似于Maven的Tycho项目:http ://eclipse.org/tycho/ ? 问题答案: 我不知道是否存在与Tycho相当的插件。请参阅此Gradle论坛条目以获取相关讨论。