ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: Ivy web site
Date Sat, 22 Dec 2007 10:37:49 GMT
I've done the change, now the generated web site is in svn:
https://svn.apache.org/repos/asf/ant/ivy/site/target/

The site on people.a.o is now just an svn co of this URL, which can easily
be updated with svn up. I have not added an svn:externals from ant site to
ivy yet, I'd like feedback from other people before doing so. If we don't
add this svn:externals, we should either upgrade ant site update cron to
call a svn up on ivy site too, or create a cron ivy site update alone.

Xavier

On Dec 22, 2007 10:03 AM, Xavier Hanin <xavier.hanin@gmail.com> wrote:

> Since everybody seems to be fine with this change on Ivy web site
> publication policy, I'll make the change now.
>
> Xavier
>
>
> On Dec 18, 2007 2:04 PM, Xavier Hanin < xavier.hanin@gmail.com> wrote:
>
> > On Dec 18, 2007 12:12 PM, < Jan.Materne@rzf.fin-nrw.de> wrote:
> >
> > > > > I havent spent any time on Ants site repo [2]. But if we think
> > > that
> > > Ivy is
> > > > > a subproject of Ant, Ivys homepage is a subpage of Ants. So we
> > > could
> > > store
> > > > > Ivys generated pages in the generated directory [3] of that repo
> > > and
> > > upload
> > > > > it via its buildfile [4].
> > > >
> > > > Or we could put generated ivy site at
> > > > https://svn.apache.org/repos/asf/ant/ivy/site/generated (to follow
> > > ant
> > > > convention) and use svn:externals in [3] to make it "part" of
> > > > ant site so
> > > > that it's updated automatically whenever svn up is called on
> > > > the site on
> > > > people.a.o. For the site generation itself, we don't use the
> > > > same technology
> > > > (anakia / xooki) and for xooki we require ant 1.7 and java 6,
> > > > so I'm not
> > > > sure merging the two site generation is a good idea (if I understand
> > >
> > > > correctly what you suggest).
> > >
> > > I thought merging the two sites (Ant+Ivy) into ant/site/generated
> > > would
> > > make
> > > the update easier. I mean updating the webserver.
> > >
> > > Having svn:external to keep them seperated would be better. Especially
> > >
> > > if the ant/site/generated
> > > does contain the generated ivy sites ...
> > >
> > > ant/site
> > >  - xdocs = svn:ext http://svn.apache.org/repos/asf/ant/core/trunk/xdocs
> > >
> > >  - core-docs = svn:ext
> > > http://svn.apache.org/repos/asf/ant/core/trunk/docs
> > >  - lib (generation tools for Ant)
> > >  - generated (the build directory)
> > >
> > > ivy/site
> > >  - ivyde = svn:ext
> > > https://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk/doc/
> > >  - xooki
> > >  - ...
> > >  - target (the build directory)
> > >
> > > ant.apache.org     = ant/site/generated
> > > ant.apache.org/ivy = ivy/site/target
> > >
> > > I think cron could sync boths ...
> >
> > If we put an svn:externals in ant/site/generated pointing
> > ant/site/generated/ivy to ivy/site/target, then the current cron would
> > update both ant site and ivy site with no change.
> >
> > Does it sound right?
> >
> > Xavier
> >
> > >
> > >
> > >
> > > Jan
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> > >
> >
> >
> > --
> >
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://ant.apache.org/ivy/
> > http://www.xoocode.org/
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
>



-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

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