I agree - although I have absolutely nothing against svn of course, or
having it available online, but I think having an 'src' package is a
must for every project. It's the quickest way to go if you only want to
view stuff - especially if you need to take it to some offline location
(laptop, or
Jeff Jensen upstairstechnology.com> writes:
> What do you find clumsy about it?
>
> I like it. Whether I have a script that does a svn co or a wget (for other
> products), either is faster than manually downloading.
>
> Partciularly, svn maintains the user workspace, removing no longer needed
>
.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of wolfgang
Sent: Tuesday, July 05, 2005 4:58 AM
To: users@maven.apache.org
Subject: Re: where's the source code package?
Emmanuel Venisse venisse.net> writes:
> Yes, you need to use subversion for obtain sources. You
Emmanuel Venisse venisse.net> writes:
> Yes, you need to use subversion for obtain sources. You can set up
> subversion to pass through firewall
able to get source by using subversion a n d ssl:
svn co https://svn.apache.org/[..]
This works to get around the firewall I'm behind but may not
WolfgangHäfelinger wrote:
Hello,
I'm about to rebuild Maven from scratch and I start to wonder how I'm
about to get
Maven's source code?
Is it really true that those Maven guys want me to use Subversion? Is it
not common
practice to provide a source code package?
There's no problem with
Hello,
I'm about to rebuild Maven from scratch and I start to wonder how I'm
about to get
Maven's source code?
Is it really true that those Maven guys want me to use Subversion? Is it
not common
practice to provide a source code package?
There's no problem with Subversion as such - it's rath
