ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gintautas Grigelionis <g.grigelio...@gmail.com>
Subject Re: Site stuff (in particular Ivy and IvyDE)
Date Tue, 20 Dec 2016 21:08:26 GMT
Perhaps you're right... I thought of splitting of /sources from SVN site
repo into separate Git repos. Then, pages compiled from /sources and/or
project documentation releases corresponding to /doc will be published to
asf-site branch in respective repo (not unlike gh-pages branch with Github
Pages). Currently existing compiled pages must be commited to the branch as
soon as it is created. That, in turn, will be picked up by gitpubsub and
pushed into repo(s) used by the website (
https://blogs.apache.org/infra/entry/git_based_websites_available). It is
not clear to me whether gitpubsub can aggregate Ant/Ivy/IvyDE. If not, we
might need one site repo for pushing all compiled pages to (instead of
having asf-site branches in every repo).

Gintas

2016-12-20 21:16 GMT+01:00 Jan Matèrne (jhm) <apache@materne.de>:

> I don't see any benefit of having one repo for all sites as they are built
> differently (ant+velocity, xooki, ...).
> Where we need the sites? Only online or in distros/manuals?
>
> I don't know the git-site-workflow, but I think I had heard something like
> gitpubsub ...
> Alternatively we could commit the generated files into a svn-repo (outch).
>
>
> Jan
>
>
> > -----Urspr√ľngliche Nachricht-----
> > Von: Gintautas Grigelionis [mailto:g.grigelionis@gmail.com]
> > Gesendet: Montag, 19. Dezember 2016 14:15
> > An: Ant Developers List
> > Betreff: Re: Site stuff (in particular Ivy and IvyDE)
> >
> > IvyDE and Ivy share styles. These are not necessary for builds (at
> > least, from what I saw with IvyDE), but it sure helps to be able to get
> > the look and feel.
> >
> > It seems sensible to me to have separate repos for site sources, one
> > per project, and another repo for publishing which would aggregate
> > built sites and all releases for all projects (that's how IvyDE builds
> > work, AFAICS).
> >
> > Gintas
> >
> > 2016-12-19 12:41 GMT+01:00 Stefan Bodewig <bodewig@apache.org>:
> >
> > > On 2016-12-15, Gintautas Grigelionis wrote:
> > >
> > > >> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bodewig@apache.org>:
> > >
> > > >> https://github.com/apache/ant-ivy-site-styles is a very curious
> > > >> case as it claims to mirror a repository that doesn't exist (I
> > > >> wanted to manually push the svn files there but fail to find the
> > repository).
> > >
> > > >> It would be good if anybody could ask INFRA in order to figure out
> > > >> what exactly the repo is mirroring as I don't see anything
> > matching
> > > >> at https://git-wip-us.apache.org/repos/asf - I'll do so myself at
> > > >> the weekend, if nobody else finds time before that.
> > >
> > > > Great! May I suggest adding repos ant-site-sources,
> > > > ant-ivy-site-sources, ant-ivyde-site-sources and ant-site (for
> > > > publishing using the git
> > > workflow)?
> > >
> > > Not exactly weekend anymore :-)
> > >
> > > https://github.com/apache/ant-ivy-site-styles and
> > > https://github.com/apache/any-ivy-site-styles
> > >
> > > seem to be the same and neither has ever been requested by us AFAICT.
> > >
> > > Assuming we wanted to restructure the site stuff, what would it look
> > > like?
> > >
> > > Do we want to move to git? All of it or just parts? How many repos do
> > > we want to use (a single one as we do right now, or one for
> > > Ant+antlibs and several for Ivy and IvyDE)? I'm not familiar with how
> > > the Ivy and IvyDE sites get built.
> > >
> > > 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
>
>

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