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

Bug 352174

Summary:	workspace migration for m2eclipse 0.12 and earlier
Product:	z_Archived	Reporter:	Shaun Elliott <javamonkey79>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	igor, jkwuc89, keesvandieren
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Shaun Elliott

2011-07-14 21:01:21 EDT

Steps to re-create:

#1 Create a project with a pre-Indigo Eclipse version + m2e
#2 Import the project into the Indigo install

The project is not recognized as a Maven project. I believe that this is because the fully qualified class name of the builder has changed. I would expect m2e to convert this over and\or detect and fix this automatically.

Comment 1 Shaun Elliott

2011-07-14 21:02:36 EDT

I'm sorry if this is a duplicate, I can't seem to find what I'm looking for.

Comment 2 Igor Fedorenko

2011-07-15 00:23:11 EDT

There are no plans to implement workspace project conversion in m2e-core. Import as Existing Maven Project and Convert to Maven Project provide a way to bring existing maven projects in m2e workspace. More advanced workspace migration logic can be implemented outside of m2e-core by a thirdparty.

Comment 3 Igor Fedorenko

2011-08-03 08:37:49 EDT

*** Bug 350701 has been marked as a duplicate of this bug. ***

Comment 4 Igor Fedorenko

2011-08-03 08:38:31 EDT

*** Bug 353751 has been marked as a duplicate of this bug. ***

Comment 5 Denis Roy

2021-04-19 13:22:33 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/