Dale Ogilvie wrote:
Well, I have tortoise installed as a general SVN client. I also have
subclipse installed for eclipse/svn integration. I then installed
m2eclipse as I have a maven managed project in SVN. I had tortoise
configured to use _svn, as I said.
So, an svn.exe in your PATH env variable is pointing to Tortoise?
So, I used "Checkout Maven Projects from SCM" and point it at the trunk
of my maven project in svn. Follows what happened after that:
...
The maven import process would proceed for some time, eventually
appearing to hang processing an individual sub-project pom. I cancelled
the hanging procedure. The projects would appear to be NOT under SCM (no
svn tag on the icon, or svn path to the right of the project name).
Opening up the projects, I see the _svn directories and other files... I
tried this a number of times.
The m2eclipse does not do anything to make project "shared with svn"
and when it works it is done by your Subclipse plugin.
So, I modified tortoise back to use .svn, rebooted as required. And
tried the "Checkout Maven Projects from SCM" again. Everything looks
great now, no _svn files, and projects appear to be svn "managed"...
This time the process seemed to finish a lot quicker as well.
I haven't done anything special to integrate tortoise, but m2eclipse is
definitely using the _svn or .svn setting configured by tortoise when it
creates the project from SVN.
You may want to check that you have installed SCM handler for
Subclipse (it is one of m2eclipse features), then m2eclipse will be
delegating directly to Subclipse when checking out projects from svn.
BTW, when your Tortoise configured to use _svn folders, what happen if
you checkout project to Eclipse using File / Import... / SVN / Project
from SVN... (or something like that, i.e. checkout it as non-Maven
project). Do you get it shared after checkout?
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
