Maven Integration for Eclipse

Directory renaming while importing maven existing project into eclipse

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.9.2
  • Fix Version/s: 0.9.3
  • Component/s: UI
  • Labels:
    None
  • Environment:
    Eclipse Europa 3.3.2, Jdk 1.6u5
  • Number of attachments :
    1

Description

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

Issue Links

This issue is duplicated by:
MNGECLIPSE-576 Import Maven Project wizard renames orginal checkout directory with a name of artifactId Critical Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Igor Fedorenko added a comment -

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

Show
Igor Fedorenko added a comment - Sergey, are you importing existing project from local filesystem or from SVN?
Hide
Permalink
Eugene Kuleshov added a comment -

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).

Show
Eugene Kuleshov added a comment - 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).
Hide
Permalink
Curt Allred added a comment -

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.

Show
Curt Allred added a comment - 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.
Hide
Permalink
Eugene Kuleshov added a comment -

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

Show
Eugene Kuleshov added a comment - 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
Hide
Permalink
Sergey Elin added a comment -

Igor, i'm importing existing project from local filesystem

Show
Sergey Elin added a comment - Igor, i'm importing existing project from local filesystem
Hide
Permalink
Sergey Elin added a comment -

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.

Show
Sergey Elin added a comment - 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.
Hide
Permalink
Thomas Diesler added a comment -

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

Show
Thomas Diesler added a comment - 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
Hide
Permalink
Eugene Kuleshov added a comment -

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

Show
Eugene Kuleshov added a comment - Fixed in trunk. When importing local Maven projects directories not renamed

People

Vote (2)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.