Check config file for the subversion. There you can find global-ignores option, where you can set filtering for target and other non-maven files (like IDE specific files).
I am following the procedure: 1) Create Maven project structure 2) Import to the Subversion (with mentioned global-ignores) 3) Now everybody can checkout 4) Every developer now can choose IDE (for example mvn eclipse:eclipse) I don't use Eclipse plugins for Maven at all, because no one is good enough for me. I am using Subclipse as the SVN client, but import and checkout I am doing manually (using svn command). Regards, Vanja On Nov 6, 2007 2:13 PM, Simon Taylor <[EMAIL PROTECTED]> wrote: > Were configuring our first Maven project and wondering if we have the > right approach. > > Were using Maven2, Subversion accessible via WebDAV, Eclipse with both > Subclipse and Maven2Eclipse plugin. > > We created a new Maven2 project in Eclipse. > We have an existing project structure that we want to convert to Maven 2 > and check in to the repository so we can then check it out and work on > it in Eclipse. > In eclipse it seems you can only check out from the repository "As a new > project" - if we do this then we don't get the Maven2 structure. > One alternative is to create the Maven2 project structure import the src > code from the filesystem and then commit the whole project to Subversion > - but ths also commits the target dir and all the compiled classes which > to my mind shouldn't live in the repository. > > Whats the right way to use Maven2, Subversion and Eclipse. > > Thanks > > Simon > > > > Simon Taylor > Service Tools Solutions (STS) Engineer > Nortel > Email [EMAIL PROTECTED] > Office +44.1279 402291 (ESN 6 742 2291) > Mobile +44.7740.533743 (ESN 748 3743) > > > >
