Hi Eugene,
Eugene Kuleshov wrote: > > That is not something provided by m2eclipse, so there isn't anything > we can do about it. You would have to request enhancements to the > corresponding plugins, e.g. Subclipse. > Ok, please support my request here in the subclipse user list: http://www.nabble.com/checkout-multiple-projects-at-once-with-rename-option-td20306899.html Eugene Kuleshov wrote: > > Because you are not telling us what Eclipse plugins you are using, I > have no way to tell if their configuration will be removed or not. So, I > suppose you will have to try it for yourself and see if it works. > Ok, I just tried. It doesn't override existing eclipse files, instead it modifies them as needed. For example, it could reorder the builders in the .project file. One thing I noticed, though. When using a naming template (<artifactId-TRUNK> for example), it writes the resulting project names into the .project files, e.g. "myartifact-TRUNK". I would suggest the following behaviour: -> use the pom project name for the .project project name if possible -> use the naming template only for naming the projects in the workspace This would be consistent with the subclipse checkout action: When checking out a single project from SVN you can give it another name, but this name is not written to the .project file, instead it's only used as project name in the workspace (and Eclipse views like Project Explorer). Does this make sense? Thanks, Holger -- View this message in context: http://www.nabble.com/Best-way-to-check-out-a-multi-module-maven-eclipse-project-tp20288854p20358141.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
