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

Bug 353173

Summary: Checkout as Maven Project fails at importing project
Product: z_Archived Reporter: Frank Jakop <frank.jakop>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: igor, jwnmulder
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
screenshot of error message
none
eclipse configuration details none

Description Frank Jakop CLA 2011-07-27 03:06:12 EDT 
Build Identifier: 20110301-1815

When I use m2e-cvs to checkout a project as Maven project, ist fails while importing the checked out project with error message 

An internal error occurred during: "Importing Maven projects".
org.osgi.framework.Version.compareTo(Lorg/osgi/framework/Version;)I



Reproducible: Always

Steps to Reproduce:
1. Go to CVS Repository Browser
2. Select project
3. right click "Check out as Maven Project"
Comment 1 Frank Jakop CLA 2011-07-27 03:06:50 EDT 
Created attachment 200419 [details]
screenshot of error message
Comment 2 Igor Fedorenko CLA 2011-07-27 03:25:45 EDT 
please attach your eclipse installation configuration details (about-eclipse->installation-detatils->configuration)
Comment 3 Frank Jakop CLA 2011-07-27 03:30:00 EDT 
Created attachment 200423 [details]
eclipse configuration details
Comment 4 Jan-Willem CLA 2011-08-03 05:47:40 EDT 
Same here. It happens when importing maven projects using 'Existing Maven Projects' and the option 'Hide folders of physically nested modules' is enabled.

Version: 1.0.100.201108010903

Stacktrace:

ava.lang.NoSuchMethodError: org.osgi.framework.Version.compareTo(Lorg/osgi/framework/Version;)I
	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.hideNestedProjectsFromParents(ProjectConfigurationManager.java:179)
	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150)
	at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164)
	at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73)
	at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 5 Igor Fedorenko CLA 2011-08-03 07:55:11 EDT 
Fixed. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=e322d67bdd77b611c67c7c153f02db1c9909a0a2

As a side note, offending code was there for very long time, so the problem is most likely caused by incompatibility between code compiled against version of osgi framework included in eclipse 3.7 and earlier eclipse version.
Comment 6 Denis Roy CLA 2021-04-19 13:24:29 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/