[#MNGECLIPSE-552] Directory renaming while importing maven existing project into eclipse

Maven Integration for Eclipse

Directory renaming while importing maven existing project into eclipse

Created: 15/Apr/08 09:47 AM Updated: 27/May/08 02:41 PM

Component/s:

Affects Version/s:

0.9.2

Fix Version/s:

0.9.3

Time Tracking:

Not Specified

File Attachments:

mylyn-context.zip (4 kB)

Environment:

Eclipse Europa 3.3.2, Jdk 1.6u5

Issue Links:

Duplicate

This issue is duplicated by:

~~MNGECLIPSE-576~~ Import Maven Project wizard renames orginal checkout directory with a name of artifactId

Description

« Hide

When importing existing multimodule project via Maven Project wizard, root directory name was changed to artifactId ant it broke catalog structure.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Igor Fedorenko added a comment - 15/Apr/08 10:14 AM

Sergey, are you importing existing project from local filesystem or from SVN?

[ Permlink | « Hide ]

Eugene Kuleshov added a comment - 15/Apr/08 11:58 AM

Sergey, also, can you please elaborate what is bad about renaming folder? In some cases we are forced to do so (e.g. when root dir is a subfolter of Eclipse Workspace).

[ Permlink | « Hide ]

Curt Allred added a comment - 15/Apr/08 02:46 PM

This project directory renaming also happens with simple (non-multimodule) projects, when importing from the local file system.

This is a very serious bug, making the plugin unusable for us.

For example our project structure is

project/trunk
- pom.xml
- src/

After importing the project, the trunk directory is renamed to the project name, breaking the code tree so svn updates no longer work.

[ Permlink | « Hide ]

Eugene Kuleshov added a comment - 15/Apr/08 02:51 PM

Curt, what version control system you are using? Updating from the renamed "trunk" folder should not be an issue with svn and cvs. I do this all the time.

Anyways, I'll look at this for 0.9.3

[ Permlink | « Hide ]

Sergey Elin added a comment - 16/Apr/08 12:27 AM

Igor, i'm importing existing project from local filesystem

[ Permlink | « Hide ]

Sergey Elin added a comment - 16/Apr/08 12:30 AM

Eugene, force renaming broke directory structure (and makes subversion insane) and it broke project building. I think this feature should be in Maven Import Wizard as an option (checkbox) or something like this.

[ Permlink | « Hide ]

Thomas Diesler added a comment - 18/Apr/08 02:50 AM

I think I found a work around for this:

#1 before importing change the artifactId in pom.xml to the directory name (i.e. trunk)
#2 do the import
#3 restore pom.xml
#4 rename the project to the artifactId

[ Permlink | « Hide ]

Eugene Kuleshov added a comment - 18/Apr/08 10:17 PM

Fixed in trunk. When importing local Maven projects directories not renamed