Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of mfncooper@gmail.com
 designates 64.233.184.206 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=ZVF/Hu5Yh+wy6fN3j8IIeKb0tpseLhY/I3ENJDLWlnrqTkUv4i3iFWHax+BuZq6VBWBKv5JbLYMIBsakerQ4ixaeNLnuBWi+F4yT3hv0k/wInBBH9+TzGO2ExDdMldhUAn0g5g487PBEzHl2ufJPoSQiiMp/ybtd3OfO0MW2XkY=
Message-ID: <16d6c6200411251244386c35cf@mail.gmail.com>
Date: Thu, 25 Nov 2004 12:44:21 -0800
From: Martin Cooper <mfncooper@gmail.com>
Reply-To: Martin Cooper <mfncooper@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>,
	Henri Yandell <flamefew@gmail.com>
Subject: Re: Migrate to SVN?
In-Reply-To: <31cc373604112512377fea78cc@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <f8b39ace0411251032257a13c8@mail.gmail.com>
	 <NBBBJGEAGJAKLIDBKJOPAENLNKAB.noel@devtech.com>
	 <31cc3736041125120425bd12c6@mail.gmail.com>
	 <2B6FF1FD-3F1F-11D9-BBED-000A95C50B1C@activemath.org>
	 <31cc373604112512377fea78cc@mail.gmail.com>

On Thu, 25 Nov 2004 15:37:42 -0500, Henri Yandell <flamefew@gmail.com> wrot=
e:
> It gave me pain; as has installing an svn server, client, Subclipse
> (Eclipse plugin), tagging in svn and generally maintaining the Berkley
> DB (it can get corrupted).
>=20
> The ASF though has much more experience with the svn server-side; so
> the only ones that would really worry me are installing a client,
> Subclipse and tagging.
>=20
> Once I figured it out, the client installed on Linux okay. On Windows
> it's a doddle, and on the Mac you do it the same way as on Linux; the
> fink install was crappy. It might be usable now, or maybe there's a
> Mac package for it.
>=20
> I've not heard that IDE plugins are any better, but I don't use them
> so it's not a biggy for me.
>=20
> The more painful tagging in svn is made up for by the advantages of
> svn, so I'm happy to embrace it.

Hmm, I actually found tagging and branching in SVN just as easy as in CVS. =
Just:

svn copy URL1 URL2

A doddle, as you might say. ;-)

--
Martin Cooper


>=20
>=20
> Hen
>=20
> On Thu, 25 Nov 2004 21:18:28 +0100, Paul Libbrecht <paul@activemath.org> =
wrote:
> > Now, for this cvs-to-svn (whichever its name is) should be working well=
.
> > The only experience I had were pretty dark.
> >
> > If someone else manages this well, I'd be happy to switch to svn as a
> > developer. I am using this myself already much.
> >
> > Has anyone experienced maven's svn support ?
> >
> > paul
> >
> > Le 25 nov. 04, =E0 21:04, Henri Yandell a =E9crit :
> >
> > > One thing to work out with Commons is whether we should move the whol=
e
> > > lot in one go; should do commons-proper then sandbox later; or do
> > > individual components one at a time as it fits their release cycles
> > > etc.
> >
> >
> > ---------------------------------------------------------------------
> >
> >
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>=20
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org