[
https://issues.apache.org/jira/browse/SLING-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607259#comment-17607259
]
Konrad Windszus commented on SLING-11590:
-----------------------------------------
Unfortunately it seems they deliberately broke with almost all pre 2.x API
(without any transition phase). Due to the use of records in the API, this also
requires the Sling IDE Eclipse Tooling to be built with Java14+.
> AbstractBundleProjectConfigurator no longer compatible with m2e 2.x
> -------------------------------------------------------------------
>
> Key: SLING-11590
> URL: https://issues.apache.org/jira/browse/SLING-11590
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.2.2
> Reporter: Konrad Windszus
> Priority: Major
>
> The following stacktrace can be observed when trying to update a Maven
> configuration of a bundle project with m2e 2.x
> {code}
> java.lang.NoSuchMethodError: 'org.eclipse.core.resources.IProject
> org.eclipse.m2e.core.project.configurator.ProjectConfigurationRequest.getProject()'
> at
> org.apache.sling.ide.eclipse.m2e.internal.AbstractBundleProjectConfigurator.configure(AbstractBundleProjectConfigurator.java:48)
> at
> org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:125)
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$6(ProjectConfigurationManager.java:475)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:350)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:262)
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:469)
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$4(ProjectConfigurationManager.java:413)
> at java.base/java.util.Collection.removeIf(Collection.java:576)
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:407)
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$3(ProjectConfigurationManager.java:339)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:350)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:262)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:205)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1093)
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:338)
> at
> org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:80)
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> due to this change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
