Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352341 - Import existing maven project vs. import existing project
Summary: Import existing maven project vs. import existing project
Status: CLOSED INVALID
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:
Depends on:
Blocks:
 
Reported: 2011-07-18 07:53 EDT by Michael Szediwy CLA
Modified: 2021-04-19 13:23 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Szediwy CLA 2011-07-18 07:53:19 EDT 
Build Identifier: I20110613-1736

I have a maven project under version control (SVN). There are the common files: .classpath .project and pom.xml. I now try to import it using "Import existing maven project". The project is imported but the .project things are ignored. 

Reproducible: Always
Comment 1 Igor Fedorenko CLA 2011-07-18 10:52:02 EDT 
This is expected behaviour -- import as maven project is fully driven by pom.xml file, not by eclipse project metadata.
Comment 2 Denis Roy CLA 2021-04-19 13:23:05 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/