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: Ivy website - fixing a Quickstart documentation live
Date Thu, 25 May 2017 08:55:14 GMT
The files mentioned in JIRA were absent for a couple of years. If they're
available, let's get them into the site repo, otherwise the css files must
be adjusted.

I remember there was a discussion about gitpubsub... perhaps if we
understand how current svnpubsub hooks are set up, going to gitpubsub
shouldn't be complicated. We'll need a dedicated repo to publish to
(ant-site-live), for starters, because that repo would aggregate publishing
from Ant, Ivy, and IvyDE. Then, we'll need a ant-site-source, and the
routines for getting parts of ant-site-live updated either from
ant-site-source or from documentation generated by builds for respective
project.

Gintas

2017-05-25 8:30 GMT+02:00 Jan Matèrne (jhm) <apache@materne.de>:

> The whole site is in svn and a server process (svnpubsub i think) is
> getting
> the 'publish' files and pushing them to the webserver which brings them
> online.
>
> We havent thought about a migrating that to git in the last few years ;)
>
> If these files are really required, I could upload them.
>
>
> Jan
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Gintautas Grigelionis [mailto:g.grigelionis@gmail.com]
> > Gesendet: Donnerstag, 25. Mai 2017 06:29
> > An: Ant Developers List
> > Betreff: Re: Ivy website - fixing a Quickstart documentation live
> >
> > Is the documentation still in SVN? IVY-1542 is about site/sources/style
> > which is shared by Ivy and IvyDE. Are there any plans about migrating
> > this to Git and separating the source repo from publication repo?
> >
> > Gintas
> >
> > 2017-05-25 6:12 GMT+02:00 J Pai <jai.forums2013@gmail.com>:
> >
> > > What would be the process of having the live docs of Ivy project
> > > updated to fix/update an issue in the documentation[1]?
> > >
> > > The quickstart documentation refers to certain log files that get
> > > auto-generated during the doc build process. It looks like those log
> > > files weren’t uploaded and are resulting in a blank text area showing
> > > up. I can run the doc generation target locally (on 2.4.0 tag) and
> > > have someone upload those files and see if shows up fine.
> > >
> > > [1] https://issues.apache.org/jira/browse/IVY-1542
> > >
> > > -Jaikiran
> > > ---------------------------------------------------------------------
> > > 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