On Dec 22, 2008, at 2:12 AM, Ilya Sterin wrote:
It it funny that you are pointing this out. The SVN restructuring
is done,
because we are planning such a move right now :)
Sounds great.
SVN will remain the master. If people just want to build from
source, or
study the code, they don't have to learn a new tool and simply do
things as
they are used to do. The idea is that developers and contributors
use Bazaar
instead of svn. Via the svn bazaar plugin we push our changes to
the svn
master or synchronize back. The problem with out current SVN
repository is
that, for the sake of simplicity, we have used it to store
binaries. It has
grown to a big size and as DVC systems check out the whole history,
this has
become a pain. Therefore we more or less clone the existing
repository to a
new one, excluding the binaries. And we change our build script to
retrieve
the binaries from an external repository.
Are you talking about binary releases? Or are you storing
dependencies there as well? I wonder the benefits of storing
dependencies, especially if they are resolved at compile time.
I intentionally had chosen the simple approach to store all of
Gradle's jar dependencies at compile time, flat in a directory without
xml descriptor files. I did this partly as a proof of concept, that
Gradle even then allows to do transitive dependency management. But
this is no longer convenient. So now we go for a 'normal' maven-like
repository based approach (although we still do it without using
pom.xmls and yet offer transitive dependencies support).
Of
course releases that include dependencies must include them. For
releases though, I'm thinking whether something like S3 would be a
better solution. It's not free, but it would be a few dollars per
month maximum for the amount that's needed I believe. There might be
some other free service out there that offers geographic content
distribution.
The codehaus repository is providing the content distribution for us.
<snip>
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
