Eugene,
Eugene Kuleshov wrote: > > Can you give us an example of what kind of plugins are configured there? > These plugins do not have any information stored in the maven pom. So it doesn't make much sense to configure them with m2eclipse. > So what is the best way to checkout the whole project with m2eclipse and > subclipse? > Eugene Kuleshov wrote: > > With flat layout it is easy. You can just select all your project > folders under trunk and use regular checkout operation. > Thanks for the tip. But when selecting multiple projects at once, you don't have the option to rename the projects in the workspace anymore. So we still have the problem to check out the trunk and branch at the same time. (Checking out each module separately is not practical for a big multi-module build.) Eugene Kuleshov wrote: > >> Can this function be used in our case, too? >> > Sure. >> Will it override or modify our version-controlled eclipse project files? >> > Yes. This feature won't use Eclipse project files. > So will it override the existing eclipse project files, loosing some stored info, or will it only modify the relevant portions of the existing files, ignoring/preserving unrelated info? Thanks, Holger -- View this message in context: http://www.nabble.com/Best-way-to-check-out-a-multi-module-maven-eclipse-project-tp20288854p20303952.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
