- Sort Score
- Num 10 results
- Language All
Results 1 - 6 of 6 for Checkstyle (0.1 seconds)
-
build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleJavadocsPlugin.java
CheckstyleExtension checkstyle = project.getExtensions().getByType(CheckstyleExtension.class); tasks.register("checkstyleApi", Checkstyle.class, task -> { task.source(extension.getDocumentedSource()); // TODO: This is ugly task.setConfig(project.getResources().getText().fromFile(checkstyle.getConfigDirectory().file("checkstyle-api.xml")));Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Sun Mar 01 05:52:34 GMT 2026 - 11.6K bytes - Click Count (0) -
build-tools-internal/build.gradle
api "org.apache.httpcomponents:httpcore:${props.getProperty('httpcore')}" compileOnly "com.puppycrawl.tools:checkstyle:${props.getProperty('checkstyle')}" runtimeOnly "org.elasticsearch.gradle:reaper:$version" testImplementation "com.puppycrawl.tools:checkstyle:${props.getProperty('checkstyle')}" testImplementation "junit:junit:${props.getProperty('junit')}" testImplementation 'com.github.tomakehurst:wiremock-jre8-standalone:2.23.2'
Created: Wed Apr 08 16:19:15 GMT 2026 - Last Modified: Mon Sep 13 18:10:22 GMT 2021 - 11.3K bytes - Click Count (0) -
CONTRIBUTING.md
- In the subsequent dialog navigate to the root `build.gradle` file - In the subsequent dialog select **Open as Project** #### Checkstyle If you have the [Checkstyle] plugin installed, you can configure IntelliJ to check the Elasticsearch code. However, the Checkstyle configuration file does not work by default with the IntelliJ plugin, so instead an IDE-specific config
Created: Wed Apr 08 16:19:15 GMT 2026 - Last Modified: Wed Sep 01 07:32:01 GMT 2021 - 36.5K bytes - Click Count (0) -
architecture/standards/0006-use-of-provider-apis-in-gradle.md
plugin, so following best practices is relatively straightforward. For core plugins in gradle/gradle, it's easy for an object to be created without applying its associated plugin. For instance, Spring has a plugin that uses the Checkstyle task directly without applying the Checkstyle plugin. Until we can provide the same guarantees for core plugins, we need to be more conservative for existing classes and not follow best practices. This means conventions need to be set in both a plugin and the...
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Thu Mar 05 12:39:41 GMT 2026 - 10K bytes - Click Count (0) -
gradle/libs.versions.toml
bouncycastle-bctls = { module = "org.bouncycastle:bctls-jdk15to18", version.ref = "org-bouncycastle" } brotli-dec = { module = "org.brotli:dec", version.ref = "brotli-dec" } checkstyle = { module = "com.puppycrawl.tools:checkstyle", version.ref = "checkstyle" } clikt = { module = "com.github.ajalt.clikt:clikt", version.ref = "clikt" } codehaus-signature-java18 = { module = "org.codehaus.mojo.signature:java18", version.ref = "codehaus-signature-java18" }Created: Fri Apr 03 11:42:14 GMT 2026 - Last Modified: Tue Mar 31 22:01:48 GMT 2026 - 12K bytes - Click Count (0) -
compat/maven-model-builder/pom.xml
<description>The effective model builder, with inheritance, profile activation, interpolation, ...</description> <properties> <!-- in: DefaultModelValidator, DefaultModelBuilder --> <checkstyle.violation.ignore>FileLength</checkstyle.violation.ignore> </properties> <dependencies> <dependency> <groupId>org.apache.maven</groupId> <artifactId>maven-api-annotations</artifactId> </dependency>
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Wed Sep 17 10:01:14 GMT 2025 - 12.3K bytes - Click Count (0)