ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <>
Subject Re: [CANCELED][VOTE] Release Ivy 2.4.0
Date Tue, 09 Dec 2014 14:12:51 GMT
Thanks for pointers stefan, i never used svn2git but i'll have a closer

We need to choose what will be our reference.

Let me give you some context :
This directory containing styles (css,etc...) is used by both website
(which is still in svn and published via svnpubsub) and project
documentation (which is in ivy's git repository). As infra was proposing
git-svn mirror it was a good compromise. Website could live using
svn:externals to fetch appropriate files, and project documentation could
use git submodules.

If we can't have this svn mirror i don't think we could move thoses file in
a new git repository as website will not be able to access it.

The ideal solutions to all this headaches would probably to have everything
in git (including ivy's website), unfortunatly as far as i know we can't
publish website via git @ASF for the moment. Infra offers a gitpubsub
feature but i read somewhere that we can't use it to publish websites.

Considering we're talking about a few files that doesn't move too often i
was suggesting duplicating them by hand and/or automating it via a script
during the release process.

2014-12-09 9:59 GMT+01:00 Stefan Bodewig <>:

> On 2014-12-09, Jean-Louis Boudart wrote:
> > If we need to find another solution then we should probably duplicate
> > styles on git as they do not move too often. We can then improve this by
> > adding some automation to replicate changes from our new reference (GIT)
> in
> > svn website like Nicolas has done when handling documentation of released
> > versions.
> I've migrated xmlunit from svn to git[1] using svn2git[2] quite easily,
> so starting with a fresh git repo and the pushing such a migrated code
> base would preserve all history.
> If you really need to keep two copies around, then "svn2git --rebase"
> might help with it - it would certainly be a manual step.
> Stefan
> [1]
> [2]
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message