gradle

OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock

由 帅比萌擦擦* 提交于 2020-12-31 05:40:54
问题 I have a Gradle project and I'm using docker in this project. When I execute the command gradlew integrationTestDocker , I get the error below. OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock 回答1: That was reported before in Oct. 2018 (issue 7043) and Nov. 2019 (issue 11520) In both cases, the suggestion was to add .gradle to the .dockerignore , in order to make sure it is not part of the docker build context. Plus this comment: After

OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock

由 陌路散爱 提交于 2020-12-31 05:39:33
问题 I have a Gradle project and I'm using docker in this project. When I execute the command gradlew integrationTestDocker , I get the error below. OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock 回答1: That was reported before in Oct. 2018 (issue 7043) and Nov. 2019 (issue 11520) In both cases, the suggestion was to add .gradle to the .dockerignore , in order to make sure it is not part of the docker build context. Plus this comment: After

Spring Boot 2.4 安装

由 与世无争的帅哥 提交于 2020-12-31 04:45:20
Spring Boot 其实是不需要安装的，一般来说针对有经验的 Java 开发者，直接将包导入到依赖中就可以了。 一个需要注意的是，你的项目如果需要转换为 Spring Boot 的项目的话，你的项目必须是 spring-boot-starter-parent 的子项目。 安装 Spring Boot Spring Boot 可以通过使用 “传统（classic）” 的 Java 开发工具或者安装一个命令行工具（command line tool）。 不管通过何种方式进行安装，你都需要 Java SDK v1.8 或者更高的版本。 在进行安装之前，你需要通过下面的命令来检查你的环境中是否已经有安装正确的 JDK 版本。 $ java -version 如果你是一个 Java 开发的初学者或者希望对 Spring Boot 有所了解，你可能希望尝试下官方提供的 Spring Boot CLI (命令行工具 Command Line Interface) 。 否则的话，你可以尝试从 “传统（classic）” 的安装介绍中开始。 针对 Java 开发者的安装指南 你可以与任何 Java 标准库相同的方式来使用 Spring Boot。 为了能够让你的项目使用 Spring Boot ，将 spring-boot-*.jar 文件放到你项目中正确的 classpath 中。

一键实现自动化部署（灰度发布）实践

由 走远了吗. 提交于 2020-12-30 10:30:16
在过去几年的DevOps的浪潮中，自动化、持续集成这两个概念早已深入人心(互联网技术人)。 比尔盖茨先生曾经都说过： “任何技术在一个业务中使用的第一条规则就是，将自动化应用到一个高效的操作上将会放大高效。第二条就是自动化应用到一个低效操作上，则放大了低效率。” 自动化部署也逐渐成为各中小型企业追求的方向，那么，今天民工哥就自动化部署的概述、自动化部署的工具、自动化部署的流程、自动化部署实践等4个方面，与大家一同来讨论、交流一下关于中小企业自动部署的问题。 1、自动化部署概述 1.1 什么是自动化部署 一句简单的话概括：部署的过程中所有的操作全部自动化，无需人工手工干预。 1.2 自动部署的好处 传统的部署方式如下： 运维人员手工使用Scp、Xftp等方式来传输数据 手工登录服务器执行git pull 、svn update等命令进行更新代码的操作 开发人员手工编译打包，然后通过内网传输给运维人员 运维人员通过rz上传的方式上传到目标服务器，然后，执行重命名原包、拷贝新包到目标目录，再执行服务应用重启命令完成整个部署过程 看似非常简单，也不是很麻烦，但是一旦项目多，部署频繁，这种情况下就会大大降低工作效率。民工哥之前工作中就有这类体验，公司的活动类项目高达100+，很多都是需要快速上线及下线、或者更新的，手工部署真的累。 传统的部署方式有以下的缺点： 整个过程都需要人员参与

Unresolved reference: compileKotlin in build.gradle.kts

由 大兔子大兔子 提交于 2020-12-30 05:33:27
问题 Kotlin project success build by build.gradle: compileKotlin { kotlinOptions.jvmTarget = JavaVersion.VERSION_1_8 } compileTestKotlin { kotlinOptions.jvmTarget = JavaVersion.VERSION_1_8 } Nice. But I need to change to build.gradle.kts : plugins { kotlin("jvm") version "1.2.10" id("application") } group = "com.myproject" version = "1.0-SNAPSHOT" application { mainClassName = "MainKt" } java.sourceCompatibility = JavaVersion.VERSION_1_8 repositories { mavenCentral() jcenter() } val kotlinVer = "1

Unresolved reference: compileKotlin in build.gradle.kts

由 一世执手 提交于 2020-12-30 05:29:27
问题 Kotlin project success build by build.gradle: compileKotlin { kotlinOptions.jvmTarget = JavaVersion.VERSION_1_8 } compileTestKotlin { kotlinOptions.jvmTarget = JavaVersion.VERSION_1_8 } Nice. But I need to change to build.gradle.kts : plugins { kotlin("jvm") version "1.2.10" id("application") } group = "com.myproject" version = "1.0-SNAPSHOT" application { mainClassName = "MainKt" } java.sourceCompatibility = JavaVersion.VERSION_1_8 repositories { mavenCentral() jcenter() } val kotlinVer = "1

How do I add KtLint style to Android Studio using Gradle?

由 亡梦爱人 提交于 2020-12-30 03:36:46
问题 I want to add the style ktlint uses to Android Studio so that when I apply formatting myself it uses the ktlint style. Based on the documentation, I installed the ktlint CLI brew install ktlint I then navigated to the root of my project and executed ktlint --android applyToIDEAProject The style now appears in my preferences for use. The issue is that the style applied through CLI uses what I think is the latest version of ktlint since my manual formatting is different from the formatting

How do I add KtLint style to Android Studio using Gradle?

由 好久不见. 提交于 2020-12-30 03:36:11
问题 I want to add the style ktlint uses to Android Studio so that when I apply formatting myself it uses the ktlint style. Based on the documentation, I installed the ktlint CLI brew install ktlint I then navigated to the root of my project and executed ktlint --android applyToIDEAProject The style now appears in my preferences for use. The issue is that the style applied through CLI uses what I think is the latest version of ktlint since my manual formatting is different from the formatting

How do I add KtLint style to Android Studio using Gradle?

由 倾然丶 夕夏残阳落幕 提交于 2020-12-30 03:36:06
问题 I want to add the style ktlint uses to Android Studio so that when I apply formatting myself it uses the ktlint style. Based on the documentation, I installed the ktlint CLI brew install ktlint I then navigated to the root of my project and executed ktlint --android applyToIDEAProject The style now appears in my preferences for use. The issue is that the style applied through CLI uses what I think is the latest version of ktlint since my manual formatting is different from the formatting

Active build variant does not have a test artifact

由 ↘锁芯ラ 提交于 2020-12-29 11:49:09
问题 I have created a new build type called 'bitrise' based on the 'debug' build variant. The instrumented androidTests build and run fine when using the 'debug' build variant however when I switch over to my new 'bitrise' build variant I get the following errors: Process finished with exit code 1 Class not found: "com.mycompany.app.ui.race.RaceFragmentUiTest" And this warning when I select "Edit Configurations..." -> "Android Instrumented Tests" Versions 'com.android.tools.build:gradle:3.5.2'
订阅 gradle