Thanks for the long response and my apologies for not being completely clear in my prior post. The bottom-line was that I did not want to have to individually Team>Share each module project when the project that contains those modules has already been checked-in.
I think a simple command line svn import from the top-level project would have imported the projects to the repository as I expected. I'd have to say from all the different issues you posted, the most likely cause is either my own misunderstanding or the following: Eugene Kuleshov wrote: > > ... > * Subclipse is known to not deal very well with nested projects, > especially if you are using Synchronze view, and to work around that I > suggest to only synchronize on the top most parent project and then > refresh the child ones if necessary (because they files will be there on > the file system) > ... > -- 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-tp22131249p22133728.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
