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

Bug 368003

Summary: Resources not copied to classpath when importing Helios project in Indigo
Product: z_Archived Reporter: Jan De Moerloose <jan.demoerloose>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: fbricon, igor
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Jan De Moerloose CLA 2012-01-06 03:03:37 EST 
Build Identifier: Version: Indigo Service Release 1 Build id: 20110916-0149

After upgrading to Indigo, i imported my old Helios-configured projects using 'Import as maven project'. The projects seemed to work fine, but after a project->clean resources where not copied to the classpath. I noticed there was an old maven builder in the project->properties->builders tab, which was reported as missing. Removing all eclipse files and reimporting the project fixed the problem.
It would be good to automatically fix the configuration or at least report a problem in the problem view.

Reproducible: Sometimes

Steps to Reproduce:
1. create project with helios
2. import with indigo
3. project->clean
Comment 1 Igor Fedorenko CLA 2012-01-06 06:19:15 EST 
m2e does not provide automatic project migration from m2e 0.12 and earlier versions. I'll keep this bug report open in case somebody wants to investigate the problem, but m2e development team does not have plans to work on it.
Comment 2 Fred Bricon CLA 2012-01-06 08:30:01 EST 
Andrew from SpringSource/STS has a conversion plugin he's willing to contribute back to m2e. See Bug 360861 for more details.
Comment 3 Igor Fedorenko CLA 2012-01-06 08:38:26 EST 

*** This bug has been marked as a duplicate of bug 360861 ***
Comment 4 Denis Roy CLA 2021-04-19 13:24:49 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/