dependency: bump maven-compiler-plugin from 3.9.0 to 3.10.0 #11313
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
|
2 of the CIs seem to have some weird errors related to |
|
I'm on it |
|
Cirrus and Appveyor are both CI hosted on Windows. |
|
The root case is apache/maven-compiler-plugin@40dd50f from apache/maven-compiler-plugin#88 |
Bumps [maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) from 3.9.0 to 3.10.0. - [Release notes](https://github.com/apache/maven-compiler-plugin/releases) - [Commits](apache/maven-compiler-plugin@maven-compiler-plugin-3.9.0...maven-compiler-plugin-3.10.0) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-compiler-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
pbludov
force-pushed
the
dependabot/maven/org.apache.maven.plugins-maven-compiler-plugin-3.10.0
branch
from
dd5c25c
to
8159a24
Compare
|
The exception is thrown here: https://github.com/openjdk/jdk17/blob/74007890bb9a3fa3a65683a3f480e399f2b1a0b6/src/hotspot/share/classfile/classFileParser.cpp#L5797 It looks like the problem is not platform dependent, but JDK dependent. |
|
Solved by turning the new feature off. |
| <configuration> | ||
| <source>${java.version}</source> | ||
| <target>${java.version}</target> | ||
| <createMissingPackageInfoClass>false</createMissingPackageInfoClass> |
There was a problem hiding this comment.
New version brings a new feature which is not stable in some environments.
For some reason, the feature is enabled by default. We don't need this feature.
|
Related issue in the tracker: https://issues.apache.org/jira/browse/MCOMPILER-205 |
|
Thank you Daniel. The correct solution is to wait for the fix. |
|
@dependabot ignore this minor version |
|
OK, I won't notify you about version 3.10.x again, unless you re-open this PR or update to a 3.10.x release yourself. |
dependabot
bot
deleted the
dependabot/maven/org.apache.maven.plugins-maven-compiler-plugin-3.10.0
branch
|
FYI, "ignore this patch version" is not documented but works and it's what I did. Just in case 3.10.1 is next... |
Bumps maven-compiler-plugin from 3.9.0 to 3.10.0.
Release notes
Sourced from maven-compiler-plugin's releases.
Commits
f4239a4[maven-release-plugin] prepare release maven-compiler-plugin-3.10.0fda9729fix typo gtrhhhrhr49a40abuse githubbd72d75back to snapshot again2863d29[maven-release-plugin] prepare release maven-compiler-plugin-3.10.0807d4e5use last release plugin version037670crestore snapshot version07d635a[maven-release-plugin] prepare for next development iterationa0fa151[maven-release-plugin] prepare release maven-compiler-plugin-3.10.0500ade4add more jdk for testing (#93)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)