I think I have come to something workable. It could be smarter to avoid any
checkout, but at least it works.
svn:external have disappeared, they are now replaced with manual git checkout.
I have made an ant target to handle it properly.
For instance, the trunk version (trunk as the name used in
Hi,
as far as I know there is no gitpubsub for the web sites so far. At least that
was the case when we migrated to git.
I had a look at the gitpubsub link that you mention Nicolas, I think this
functionality is only available to setup some automation around git commits,
for instance for event
Le 26 oct. 2014 à 20:16, Jean-Louis Boudart a
écrit :
> Would it be possible to have everything on git ?
> Looks like there is a gitpubsub feature available[1]
I don’t know either what is possible, I am not familiar with gitpubsub and
submodule. That’s why I am asking here.
> Another option c
Would it be possible to have everything on git ?
Looks like there is a gitpubsub feature available[1]
Another option could be to use svn client for github (but this relies on
github infra not ASF one :/) [2].
A "manual" solution could be to have website + released documentation on
svn. Git could
Now that the Ivy’s code source is in git, but the site is still managed in svn,
how do we update the doc of Ivy trunk in the site ?
How can I update this : http://ant.apache.org/ivy/history/trunk/index.html
We’ll have a similar issue when we will release, we will need to publish the
released doc
