Holger Brands wrote:
That is intentional.
Yep, I know. I just wanted to let you know what happened ;-)
Ah, thanks. :-)
The subclipse checkout action manages this somehow.
It creates a project directory with the new name in the workspace, but the
.project file keeps the original project name. After checkout the Project
explorer shows the project with the new name.
I'll enter an enhancement request for this...
I will have to look at that, but there is significant difference
between how projects are created by subclipse and m2eclipse. The former
is copying resources after creating project in workspace while the
latter imports projects right from their location.
But I noticed another thing, doing the following:
- "Checkout as Maven project" of a multimodule build with flat layout (as
outlined in my first message)
- Later, delete all the projects (with content) from within Eclipse
---> the temp directory "maven.1225977330365" with a nested ".svn" dir is
left in the workspace dir
I'm using m2eclipse v0.9.6.20080905-0917 with subclipse 1.4.5 on Eclipse 3.4
and Windows XP.
Should I submit an issue or is Eclipse/subclipse responsible?
This is how m2eclipse works. Basically it checks out selected location
locally and then imports all Maven projects it could find from that
location. In your case location selected for checkout haven't had any
projects in it, but it is not always the case. One may suggest to rename
or move found projects around, but in that case we'll have to deal with
bunch of corner cases (e.g. naming conflicts) and that would create more
issues, so it doesn't see worth the effort.
It is still a good idea to submit an issue for this to leave the
record, but because project deletion is handled by Eclipse, right now I
can't think of a way how to remove some folder that is outside of
Eclipse workspace, so please don't expect a quick fix.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
