You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Nicolas Lalevée <ni...@hibnet.org> on 2009/07/15 10:54:35 UTC
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 <xa...@gmail.com>
wrote:
> On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
> <ma...@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-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@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-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Ivy site and old versions
Posted by Maarten Coene <ma...@yahoo.com>.
Thanks Nicolas,
I've deployed the website for Ivy 2.1.0-rc2, and it was much easier (and faster) indeed :-)
We'll have to wait some hours before the result will become visible on http://ant.apache.org/ivy
btw, I'll send the announcement of the new Ivy release when the new site will be online...
regards,
Maarten
----- Original Message ----
From: Nicolas Lalevée <ni...@hibnet.org>
To: Ant Developers List <de...@ant.apache.org>
Sent: Sunday, July 19, 2009 4:32:44 PM
Subject: Re: Ivy site and old versions
Le 16 juil. 09 à 00:14, Nicolas Lalevée a écrit :
>
> 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
I have updated the build and created the website. I have also updated the release docs.
Note on the implementation of the generation of the website:
* to make the breadcrumb in the "external" doc I have made the generate-history-ivy* targets modify the toc.json in the imported svn tags. So we have to be careful to not commit thoses modification. This is not optimal but it can be improved later.
* the generate-history targets are always generating everything, they do not use the uptodate feature. This can be painfull while updatin the trunk version for instance. This is not a design choice, I just didn't took time to do it. It can be added later.
* in IvyDE's website there were no printer friendly version of the documentation. I have enable it but yet the link in the non-html page are not pointing to the generated book.html. And in the imported tags we don't have the printer friendly templates. So for now, before I generated the website I copied manually the one from the root of the IvyDE website so they can be used by xooki. All of this can be fixed later I think.
And I have deployed it here (not visible yet as I write this mail):
http://ant.apache.org/ivy-new/
So if everybody is OK with it, the new version could be deployed as Maarten will have the Ivy release deployed.
And I have found in /www/ant.apache.org : ivy-2.0.0-backup, ivy-rc1-backup, and ivy.bck. Maarten and Xavier you are holding some write permission on them, maybe you could cleanup these backup when you will have some time.
Nicolas
>
>
>>
>> Maarten
>>
>>
>>
>> ----- Original Message ----
>> From: Nicolas Lalevée <ni...@hibnet.org>
>> To: Ant Developers List <de...@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 <xa...@gmail.com>
>> wrote:
>>> On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
>>> <ma...@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-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@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-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
>
---------------------------------------------------------------------
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
Re: Ivy site and old versions
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 16 juil. 09 à 00:14, Nicolas Lalevée a écrit :
>
> 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
I have updated the build and created the website. I have also updated
the release docs.
Note on the implementation of the generation of the website:
* to make the breadcrumb in the "external" doc I have made the
generate-history-ivy* targets modify the toc.json in the imported svn
tags. So we have to be careful to not commit thoses modification. This
is not optimal but it can be improved later.
* the generate-history targets are always generating everything, they
do not use the uptodate feature. This can be painfull while updatin
the trunk version for instance. This is not a design choice, I just
didn't took time to do it. It can be added later.
* in IvyDE's website there were no printer friendly version of the
documentation. I have enable it but yet the link in the non-html page
are not pointing to the generated book.html. And in the imported tags
we don't have the printer friendly templates. So for now, before I
generated the website I copied manually the one from the root of the
IvyDE website so they can be used by xooki. All of this can be fixed
later I think.
And I have deployed it here (not visible yet as I write this mail):
http://ant.apache.org/ivy-new/
So if everybody is OK with it, the new version could be deployed as
Maarten will have the Ivy release deployed.
And I have found in /www/ant.apache.org : ivy-2.0.0-backup, ivy-rc1-
backup, and ivy.bck. Maarten and Xavier you are holding some write
permission on them, maybe you could cleanup these backup when you will
have some time.
Nicolas
>
>
>>
>> Maarten
>>
>>
>>
>> ----- Original Message ----
>> From: Nicolas Lalevée <ni...@hibnet.org>
>> To: Ant Developers List <de...@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.hanin@gmail.com
>> >
>> wrote:
>>> On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
>>> <ma...@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-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@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-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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Ivy site and old versions
Posted by Nicolas Lalevée <ni...@hibnet.org>.
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 <ni...@hibnet.org>
> To: Ant Developers List <de...@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.hanin@gmail.com
> >
> wrote:
>> On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
>> <ma...@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-unsubscribe@ant.apache.org
>>> For additional commands, e-mail: dev-help@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-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
Re: Ivy site and old versions
Posted by Maarten Coene <ma...@yahoo.com>.
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?
Maarten
----- Original Message ----
From: Nicolas Lalevée <ni...@hibnet.org>
To: Ant Developers List <de...@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 <xa...@gmail.com>
wrote:
> On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
> <ma...@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-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@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-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
Re: Ivy site and old versions
Posted by Xavier Hanin <xa...@gmail.com>.
2009/7/15 Nicolas Lalevée <ni...@hibnet.org>
> 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?
Excellent idea Nicolas! A big +1 for this change!
Xavier
>
>
> 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 <xa...@gmail.com>
> wrote:
> > On Tue, Mar 31, 2009 at 11:59 PM, Maarten Coene
> > <ma...@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-unsubscribe@ant.apache.org
> >> For additional commands, e-mail: dev-help@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-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@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/