-
Updated
Jun 6, 2020 - Kotlin
gradle-plugin
Here are 921 public repositories matching this topic...
The tool generates code that causes PMD UnnecessaryModifier warnings for generated enums .
(https://pmd.github.io/latest/pmd_rules_java_codestyle.html#unnecessarymodifier)
It might make sense to change the autogenerated code not to have
private SomeEnum(String value) {
this.value = value;
}
but
SomeEnum(String value) {
this.value = value;
}
-
Updated
Jun 3, 2020 - Kotlin
I was working through setting up detekt in a sample Android project, and ran into some odd/confusing behavior. This occurred with version 1.6.0, but also seemed to occur if I tried older versions as well.
I set things up in my root level project as per the instructions here, and applied the plugin to my mai
-
Updated
Jun 6, 2020 - Kotlin
Thank you for this project!
I have been struggling to work out how best to configure a CI for using DependencyCheck.
For example, I'd like to use the caching feature of GitHub actions with DependencyCheck to avoid redownloading all the CVEs on each build.
- Is there a shared cache I can refer to?
- If not; what's the "right" way to set up a shared cache for my project?
Ideally, this
It runs on ASTs, so it can run in parallel to compilation.
As a potential followup, we can maybe look at making lint optionally run as an implicit concurrent action of building a src target
-
Updated
May 31, 2020 - Java
-
Updated
Feb 9, 2020 - Kotlin
-
Updated
May 31, 2020 - Groovy
-
Updated
May 6, 2020 - Java
-
Updated
Jan 16, 2020 - Java
Hi!
release {
versionPropertyFile = "version.properties"
afterEvaluate {
buildTasks = listOf(":aem:assembly:full:build")
}
}
afterEvaluate {
throw GradleException("${project.version}")
}
ends with
* What went wrong:
A problem occurred configuring root project 'example'.
> unspecified
however if I put version to `gradle.pr
-
Updated
Oct 14, 2016 - Groovy
vendorPath not match
When building github.com/AsynkronIT/protoactor-go we got the following error:
vendor dependency golang.org/x/time:github.com/hashicorp/consul: commit='a86d11ec0aaadf6965014abd0030085d67454406', urls=[https://github.com/hashicorp/consul.git, git@github.com:hashicorp/consul.git]/vendor/golang.org/x/time/rate does not exist in transitive dependencies of github.com/hashicorp/consul#a86d11ec0
When I use the gradle plugin with Gradle 6, I get the following deprecation warning.
> Task :generateTypeScript
Running TypeScriptGenerator version 2.21.588
The compile configuration has been deprecated for resolution. This will fail with an error in Gradle 7.0. Please resolve the compileClasspath configuration instead. Consult the upgrading guide for further information: https://docs.grad
-
Updated
Feb 11, 2018 - Java
I'd like Shot to tell me if it finds some reference images that are not being used while running it. When you decide to rename your tests it often leaves some orphan screenshots so I think it's great if Shot displayed a warning in that situation.
-
Updated
May 18, 2020 - Kotlin
Starting Gradle 5.1 it is possible to pin repository to specific artefact. Plugin should check Gradle version and add a repository configuration for ktlint. This should simplify plugin setup.
Docs to look into: https://docs.gradle.org/current/javadoc/org/gradle/api/artifacts/repositories/MavenArtifactRepository.html#mavenContent-org.gradle.api.Action-
The plugin defaults to translate jsps into java files but not compile those jsps for war file packaging. The tomcatJasper task is dependent on classes. Since classes runs first, your existing .java files will be turned into .class files, then your jsps will be turned into .java files. This is the correct ordering as your .class files may be required to translate or compile your jsp / jsp java f
The MOE_HOME env var is no longer used by MOE, the messages that still mention it should be cleaned up.
-
Updated
Jan 4, 2020 - Groovy
-
Updated
May 31, 2020 - Kotlin
-
Updated
Mar 8, 2018 - Java
-
Updated
May 7, 2020 - Java
Improve this page
Add a description, image, and links to the gradle-plugin topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the gradle-plugin topic, visit your repo's landing page and select "manage topics."
Copied from briandealwis/cram#5: @student-06 asked