Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344823

Summary: m2e-wtp linked in wrong version in marketplace
Product: z_Archived Reporter: Konrad Windszus <konrad_w>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: bimargulies, igor, mohsens
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Konrad Windszus CLA 2011-05-05 06:57:48 EDT
In the current milestone (m7), the wrong version of m2e-wtp is downloaded over the M2E marketplace. Version 0.13.0.201103072204 is downloaded, which is imcompatible with m2e m7 and the latest trunk. Please update the link to a newer version (compare with issue https://issues.sonatype.org/browse/MECLIPSEWTP-115)
Comment 1 Igor Fedorenko CLA 2011-05-09 09:39:39 EDT
Updated m2e-wtp version in m2e marketplace to 0.13.0.201105040943.
Comment 2 Igor Fedorenko CLA 2011-05-10 00:26:06 EDT
*** Bug 345221 has been marked as a duplicate of this bug. ***
Comment 3 Mohsen Saboorian CLA 2011-05-10 00:43:27 EDT
After updating to m2e-wtp 0.13.0.201105040943, I'm getting the new exception:

java.lang.NoSuchMethodError: org.eclipse.m2e.jdt.IClasspathEntryDescriptor.getClasspathEntry()Lorg/eclipse/jdt/core/IClasspathEntry;
at org.maven.ide.eclipse.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:335)
at org.maven.ide.eclipse.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:94)
at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:294)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:402)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:383)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:410)
at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:229)
at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:218)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:724)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:847)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:280)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:280)
at org.eclipse.m2e.core.ui.internal.UpdateConfigurationJob.runInWorkspace(UpdateConfigurationJob.java:87)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 4 Igor Fedorenko CLA 2011-05-20 12:02:18 EDT
*** Bug 346700 has been marked as a duplicate of this bug. ***
Comment 5 Denis Roy CLA 2021-04-19 13:23:18 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/