Le 15 juil. 09 à 22:22, Maarten Coene a écrit :
Excellent idea!
I can wait a few days before finalizing the release, but I would
like to have it finished before 21/07, do you think this could be
possible?
I will probably have time to do it this Friday, or at least Saturday.
I will keep you posted.
Nicolas
Maarten
----- Original Message ----
From: Nicolas Lalevée <nicolas.lale...@hibnet.org>
To: Ant Developers List <dev@ant.apache.org>
Sent: Wednesday, July 15, 2009 10:54:35 AM
Subject: Re: Ivy site and old versions
let's undig an old thread,
I may have a solution to this. I recently added a feature in xookie
so that
an entry in the toc can be absolute url rather than a document in
the tree.
So we can probably use it to leverage the size the toc on both Ivy and
IvyDE websites.
I suggest we don't import the subtree of any version of the
documentation
in the history menu and use urls that point to an "external" toc. For
instance history/2.x/2.1.x/2.1.0-rc1 will be an url to
http://ant.apache.org/ivy/history/2.x/2.1.x/2.1.0-rc1/index.html,
and on
that last page we will see only the toc of the 2.1.0-rc1
documentation.
And the only subtree we would import would be the documentation of the
latest milestone, the documentation which is not in the history
subtree.
Then each time we release a new version, we will:
* add in the history a entry for the new version
* generate the subtree for that new history entry
* update the latest milestone svn:external
* regenerate the entire website, which won't include any of the
documentation in the history
WDYT?
And Maarten, if you can hold up for few days the deployment of the Ivy
release, I can have this implemented so you will have less pain while
updating the site (you will beta-test that new process thought ;) ).
Nicolas
On Wed, 8 Apr 2009 19:31:38 +0200, Xavier Hanin <xavier.ha...@gmail.com
>
wrote:
On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
<maarten_co...@yahoo.com>wrote:
Hi,
regenerating and committing the Ivy site takes a lot of time at the
moment.
I wondered if we could speed that up by cleaning up the history
part of
the
site. For instance, is it really necessary we still have the
documentation
of ivy-2.0.0-alpha1 online?
I agree we could clean up the online history. What would be even
better
is
to load the navigation tree separately from the rest of the page so
that
we
would not have to update all pages whenever the navigation tree
changes...
Xavier
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
--
Xavier Hanin - 4SH France
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
