Maybe I didn't clarify these were several projects that have never been checked into svn before, hence the need to svn import.
I was commenting on the process I went through to add them to version control for the first time. It is not necessarily a bug, but more along the lines of a feature request, and I wouldn't want to open an issue unless it is confirmed by somebody. Some more clarity: when I talk about "svn import," the Eclipse equivalent function would be Team>Share. These should not be confused with the Eclipse Import... function. Simple Example: maven-project-P1 --> maven-project-P1-module1 --> maven-project-P1-module2 About these projects: * none have been checked into SVN before * each is a separate project in Eclipse What is the recommended way to add all these projects to version control (i.e. svn import)? In my case, I attempted to simply svn import maven-project-P1 and was hoping, because the module projects are nested on the filesystem, that this check-in would include the nested directories (I'm pretty sure this would be the behavior from the command-line when using "svn import" from the maven-project-P1 directory). However, the subdirectories were hidden from view in the synchronize view, and therefore were not checked-in. I could have, at that point, decided to add each one individually (Team>Share), but that was undesirable because I had so many module projects to check-in. I was hoping for a more elegant way of going about it. Thanks for all your feedback. I anticipate that the next time I create a new module, I'll probably figure out whether or not I was just misinterpreting. -- View this message in context: http://www.nabble.com/High-jinks-w--m2Eclipse%2C-Maven-modules%2C-subclipse%2C-and-svn-import-%28a.k.a.-Team-%3E-Share-Project...%29-tp22131249p22138686.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
