Dan North <dan@tastapod.com> wrote on 11/09/2005 09:31:25 AM:
> Woohoo! That's exactly what I was looking for, thanks Miha.
>
> Now, does anyone know the "default location" for javasvn client? What I
want
> to do is get the team using a common config without them having to
install the
> svn command line client.
>
> I guess I could just put my subversion config under source control and
get
> them to point to a local checkout of it.
I would step back for a second.
My assumption would be that JavaSVN already looks at the Subversion config
file. I was greatly puzzled by your initial question since I cannot
understand why this wouldn't already work. I didn't reply immediately
because I am expecting Alex at tmate to respond.
If JavaSVN doesn't support this, then setting that preference isn't going
to do anything. All that preference does is override the location of the
config file. If you do not set it, the default area will be used. I am
not 100% convinced that the Subclipse feature of setting the area even
works. When I tested it once, it didn't seem like it was working. That
being said, I have been working in this general area of the code lately
and it did seem like everything was correctly in place for it to work, so
maybe it does.
Anyway, if JavaSVN is not alredy using your Subversion config file, then
setting the location of it isn't likely to make a difference.
If possible, I would recommend you stick with configuring the default
Subversion config file. That way, you know it will work for any
Subversion client.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Nov 10 01:40:49 2005