Compare commits

...

4 Commits

Author SHA1 Message Date
Trass3r
23a72e6969
Merge a8ea2555c9 into 7a445ee88d 2023-12-21 07:56:52 -07:00
Michael Keppler
7a445ee88d
Fix typo in configuration example (#572) 2023-12-21 10:03:21 +01:00
Trass3r
a8ea2555c9
fix spaces 2023-12-01 01:12:38 +01:00
Trass3r
817fb5daef
add javac problemMatcher 2023-12-01 01:02:26 +01:00
2 changed files with 14 additions and 2 deletions

14
.github/java.json vendored
View File

@ -9,6 +9,18 @@
"message": 3
}
]
},
{
"owner": "javac",
"pattern": [
{
"regexp": "^([^:]+):(\\d+): (warning|error): (.+?)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
]
}
]
}
}

View File

@ -463,7 +463,7 @@ The result is a Toolchain with entries for JDKs 8, 11 and 15. You can even combi
architecture: x64
```
This will generate a Toolchains entry with the following values: `version: 1.6`, `vendor: jkdfile`, `id: Oracle_1.6`.
This will generate a Toolchains entry with the following values: `version: 1.6`, `vendor: jdkfile`, `id: Oracle_1.6`.
### Modifying The Toolchain Vendor For JDKs
Each JDK provider will receive a default `vendor` using the `distribution` input value but this can be overridden with the `mvn-toolchain-vendor` parameter as follows.