Eugene Kuleshov wrote: > > That is intentional. >
Yep, I know. I just wanted to let you know what happened ;-) Eugene Kuleshov wrote: > > I don't think it works like that. When project is imported or created > Eclipse reads its name from .project file. > Anyway, you need to submit an enhancement request, then someone might > want to look at the patch. > 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... 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? Thanks, Holger -- View this message in context: http://www.nabble.com/Best-way-to-check-out-a-multi-module-maven-eclipse-project-tp20288854p20362119.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
