Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352174 - workspace migration for m2eclipse 0.12 and earlier
Summary: workspace migration for m2eclipse 0.12 and earlier
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 350701 353751 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-07-14 21:01 EDT by Shaun Elliott CLA
Modified: 2021-04-19 13:22 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shaun Elliott CLA 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 CLA 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 CLA 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 CLA 2011-08-03 08:37:49 EDT
*** Bug 350701 has been marked as a duplicate of this bug. ***
Comment 4 Igor Fedorenko CLA 2011-08-03 08:38:31 EDT
*** Bug 353751 has been marked as a duplicate of this bug. ***
Comment 5 Denis Roy CLA 2021-04-19 13:22:33 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/