micronaut-build icon indicating copy to clipboard operation
micronaut-build copied to clipboard

Common Gradle build scripts

Results 38 micronaut-build issues
Sort by recently updated
recently updated
newest added

This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.sonarsource.scanner.gradle:sonarqube-gradle-plugin](http://redirect.sonarsource.com/doc/gradle.html) ([source](https://togithub.com/SonarSource/sonar-scanner-gradle)) | `4.0.0.2929` -> `4.4.1.3373` | [![age](https://developer.mend.io/api/mc/badges/age/maven/org.sonarsource.scanner.gradle:sonarqube-gradle-plugin/4.4.1.3373?slim=true)](https://docs.renovatebot.com/merge-confidence/) |...

dependency-upgrade

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [clipboard.js](https://clipboardjs.com) ([source](https://togithub.com/zenorocha/clipboard.js)) | major | `1.5.13` -> `2.0.11` | --- > [!WARNING] > Some dependencies...

dependency-upgrade

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [clipboard.js](https://clipboardjs.com) ([source](https://togithub.com/zenorocha/clipboard.js)) | minor | `1.5.13` -> `1.7.1` | --- > [!WARNING] > Some dependencies...

dependency-upgrade

Projects generating documentation from ascii doc files and having `api:` links will always add `io.micronaut` prefix to the API links even when API does not belong to Micronaut libraries. Would...

At some point (perhaps with a Gradle update?) the JaCoCo reports stopped working. For example: https://github.com/micronaut-projects/micronaut-openapi/actions/runs/5329318280/jobs/9654878870?pr=1059 ``` No coverage report can be found with sonar.coverage.jacoco.xmlReportPaths='/home/runner/work/micronaut-openapi/micronaut-openapi/build/reports/jacoco/testCodeCoverageReport/testCodeCoverageReport.xml'. Using default locations: target/site/jacoco/jacoco.xml,target/site/jacoco-it/jacoco.xml,build/reports/jacoco/test/jacocoTestReport.xml ```...

type: bug

Currently our build plugins prevent us from using Gradle's configuration cache. It would be good to support it, as this would speed up things, especially in the IDE when running...

type: improvement

### Feature description For each release we should send a PR to https://github.com/oracle/graalvm-reachability-metadata/blob/master/library-and-framework-list.json with a list of modules that are tested with and known to work with native image and...

Explore moving our builds to use [Gradle Toolchains](https://docs.gradle.org/current/userguide/toolchains.html), which should allow us to support builds of future Java versions/GraalVM versions more easily.

relates-to: graal

If you run the `JapiCmp` task from 2 different folders with the same inputs, you can't benefit from Gradle build cache as one of the input (`richReport.rules`'s Map) is using...

### Issue description It could be easily improved if we used an interface backed by a `@ConfigurationProperties` class with setters and and getters. The setter javadoc would be used. Currently,...