Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excavator: Upgrades Baseline to the latest version #2446

Merged
merged 1 commit into from
Sep 12, 2022

Conversation

svc-excavator-bot
Copy link
Collaborator

@svc-excavator-bot svc-excavator-bot commented Sep 2, 2022

excavator is a bot for automating changes across repositories.

Changes produced by the roomba/latest-baseline-oss check.

Release Notes

4.154.0

Type Description Link
Improvement The JUnits reports plugin is no longer applied by default. Test reports now use the standard output locations from Gradle conventions. palantir/gradle-baseline#2355

4.155.0

Automated release, no documented user facing changes

4.156.0

Type Description Link
Fix Fix BaselineJavaVersion checkstyle configuration on gradle < 7.5 palantir/gradle-baseline#2360

4.157.0

Type Description Link
Improvement Make task initialization lazier in the junit-reports plugin. palantir/gradle-baseline#2364

4.158.0

Type Description Link
Fix Make the checkUnusedDependencies tasks added by baseline-exact-dependencies compatible with Gradle's configure-on-demand feature. palantir/gradle-baseline#2363

4.159.0

Type Description Link
Improvement Add an errorprone check and typed annotation for Javax -> Jakarta

There is a certain class of very problematic cases whereby if you have
a method such as the following:

<br>myJerseyResource.register(/* this is of type Object */ object);<br>

Then if you supply a resource which includes any javax.ws.rs
annotations on it, then those will not be registered if your Jersey
version is 3.x or later (and you'll only find this out at runtime).

The opposite is also true if you try to supply resources annotated
with jakarta.ws.rs to Jersey 2.x.

To address this, this commit attempts to add an errorprone check
which lets implementors add an annotation @ForbidJavax to methods
which have been knowingly migrated to Jakarta EE9 and cannot
accept legacy javax types.
palantir/gradle-baseline#2366

4.160.0

Type Description Link
Fix Workaround to IDEA-301084 palantir/gradle-baseline#2368

4.161.0

Type Description Link
Fix Reverts a change introduced to baseline-java-version 4.160.0, which was causing failures on multi-project builds. palantir/gradle-baseline#2369

4.162.0

Type Description Link
Feature java versions preview enhancements

+ support setting preview on a project-by-project basis.
+ Fixes #2340
+ fails more elegantly if javaVersions is set on not-the-root.
palantir/gradle-baseline#2376

4.163.0

Type Description Link
Fix Fix interface visibility bug palantir/gradle-baseline#2379

To enable or disable this check, please contact the maintainers of Excavator.

@svc-excavator-bot svc-excavator-bot force-pushed the roomba/latest-baseline-oss branch from 02743ca to d976a4f Compare September 12, 2022 16:27
@bulldozer-bot bulldozer-bot bot merged commit ea35adf into develop Sep 12, 2022
@bulldozer-bot bulldozer-bot bot deleted the roomba/latest-baseline-oss branch September 12, 2022 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants