[
https://issues.apache.org/jira/browse/SLING-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769618#comment-17769618
]
mainagioia commented on SLING-11590:
------------------------------------
No, the nightly build itself works; this temporary fix is for cases when this
fix is needed in Eclipse plugins which have 1.2.2 version as a dependency. For
example, this problem arises in latest AEM Tools for Eclipse, which has 1.2.2
as a dependency, in which "Maven - Update project" no longer works.
If I try to install nightly build of Sling, Eclipse installer requires
uninstalling AEM Tools because of the changed dependency; by taking the JAR I
modified and replacing it in Eclipse plugins directory, AEM Tools and this
"temporary" version of Sling Tools can coexist... obviously until 2.0.0 is
released and AEM Tools (and others) update their dependency requirement.
> 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
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Sling Eclipse IDE 2.0.0
>
> Attachments: AbstractBundleProjectConfigurator.java,
> ContentPackageProjectConfigurator.java, MavenProjectUtils.java,
> org.apache.sling.ide.eclipse-m2e-ui_1.2.2.jar
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
