-
Notifications
You must be signed in to change notification settings - Fork 114
Upgrade to Eclipse 2022-09 #342
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
Comments
Thanks for the report. Adapting to the breaking API changes is further complicated by the fact that m2e-core requires Java 17. |
https://github.com/wilkinsona/spring-javaformat/tree/m2e-2.0. I haven't yet checked if JDT has moved to Java 17 as well. |
Just tried to build the m2e-2.0-branch of the fork: Out of the box I was not able to package the whole project but after disabling some modules and excluding some plugins I got it working. (I used the sdkman environment) After installing the plugin in 2022-09 with the generated site-archive, at first glance everything was alright ("Update Maven Project" was working, Copyright header was generated, auto-formatting worked, ...) Reasons why I had to disable some modules/exclude some plugins:
Diffs I made to package the project:
|
Superseded by #352 |
During "Updating Maven Project" in Eclipse 2022-09, a
NoSuchMethodException
occurs. Here is the output of the Eclipse Error Log:(If helpful) here is the session data:
After the update from Eclipse 2022-06 to 2022-09,
org.eclipse.m2e:m2e-core:2.0.3
is in use, and it looks like several classes were replaced by records.ProjectConfigurationRequest
is one of those replaced classes:https://github.com/eclipse-m2e/m2e-core/blob/2.0.3/org.eclipse.m2e.core/src/org/eclipse/m2e/core/project/configurator/ProjectConfigurationRequest.java
Here is the commit with the replacement of classes with records: eclipse-m2e/m2e-core@c3ade99
The text was updated successfully, but these errors were encountered: