ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Matèrne (jhm) <apa...@materne.de>
Subject AW: [CANCELED][VOTE] Release Ivy 2.4.0
Date Wed, 10 Dec 2014 08:28:55 GMT
Security hint: 'pushing' is not as secure as 'polling' here ... Maybe
passwords have to be configured...

Jan

> -----Ursprüngliche Nachricht-----
> Von: Jan Matèrne (jhm) [mailto:apache@materne.de]
> Gesendet: Mittwoch, 10. Dezember 2014 07:57
> An: 'Ant Developers List'
> Betreff: AW: [CANCELED][VOTE] Release Ivy 2.4.0
> 
> >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.
> 
> Would a Jenkins job help here?
> It could build the website from git and 'push' (not git push ;) it
> somewhere.
> 
> 
> Jan
> 
> 
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Antoine Levy Lambert [mailto:antoine@gmx.de]
> > Gesendet: Mittwoch, 10. Dezember 2014 01:18
> > An: Ant Developers List
> > Betreff: Re: [CANCELED][VOTE] Release Ivy 2.4.0
> >
> > Yes !!!
> >
> > Antoine
> > On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bodewig@apache.org>
> wrote:
> >
> > > On 2014-12-09, Jean-Louis Boudart wrote:
> > >
> > >> 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.
> > >
> > >> 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.
> > >
> > > OK, I think I understand.  If this is really only needed for a
> > release
> > > build, having the build process fetch them from svn (which I think
> > you
> > > are suggesting) seems to be a good choice.
> > >
> > > Stefan
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> > commands, e-mail: dev-help@ant.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org



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


Mime
View raw message