I'm ready to give up on this ... after numerous tries. It seems to me the documentation as stated in the guide is wrong. The -import existing projects- 'breaks' the connection the sources initially have with subversion.
So as it says in the guide: "The result is equals to checking out the whole project from the command line, running mvn eclipse:eclipse and finally importing the projects into your eclipse workspace. In both cases you will be able to synchronize your changes using eclipse." Simply is not true! Can somebody confirm this, Thanks, Jan. > Hi, > > (Using Maven 2.0.4) > > I'm trying to figure out how to use a (Maven) multi module project in > Eclipse where Subversion is the SCM. Following the "Guide to using Eclipse > with Maven 2.x" somehow doesn't do it for me. > > Things I don't understand: > > + why should I remove .project, .classpath ? > > + given the fact that I have indeed thrown about .project, .classpath > from the modules and have checked this in into subversion, how comes > that when I start a completely new workspace and import the modules > I end up with resources not being 'connected' anymore to subversion? > > + I've read somewhere that flattening the project layout, doesn't work due > to issues with the Maven release plugin. From JIRA it seems this is > still > the case. Anyone now whether there are any workarounds for this and if > their are other issues in flattening the layout? > > Thanks. > Jan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
