Zemian Deng wrote:
I notice that when importing a Maven Project, it force the project
directory name to be renamed to same as the artifactId name. Is this
nessacery?
It is an Eclipse limitation. If you import projects into Eclipse
workspace folder, the project name should match folder name. It is not
an issue if you specify an alternative location for those projects.
I've added FAQ entry for that
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-rename
If I were to work on a two version of the same project like the trunk
and a maintenance branch, then it fail to import the second one into a
Eclipse workspace because it claim the project already exists. Is this
normal?
Again, yes. By default, Maven project import is using artifactId as
project name, but you can specify alternative name template/pattern in
Advanced section of the project import wizards (e.g. you can use
[artifactId]-[version] template). Note that you need to make sure that
artifact versions are different between those projects, or else
dependency resolver will get really confused.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
