[Result] [VOTE] Release of Apache IvyDE 2.0.0.alpha1 (take 2)

[Nicolas Lalevée]

After one week of vote, here are the results:
3 binding +1
2 non binding +1

The release is accepted !

So now I will push the binaries in dist.
I will regenerate entirely the ivyde website, which will include the  
updatesite with its mirror configuration.
I will tag the trunk branch (we talked about tagging xooki, but I  
don't know where...? and actually I am reconsidering it as xooki is  
not changing that much, is it really needed ?)
And finally sent an announcement (after discussing it on the mailing  
list)

Nicolas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xavier Hanin]

On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée <nicolas.lalevee@...>
wrote:

> After one week of vote, here are the results:
> 3 binding +1
> 2 non binding +1
>
> The release is accepted !

Great! Congratulations to the whole team and especially you, Nicolas!

>
>
> So now I will push the binaries in dist.
> I will regenerate entirely the ivyde website, which will include the
> updatesite with its mirror configuration.

That sounds nice.

>
> I will tag the trunk branch (we talked about tagging xooki, but I don't
> know where...? and actually I am reconsidering it as xooki is not changing
> that much, is it really needed ?)

We didn't tag it for Ivy releases, but it would be better to do it. But
indeed I don't know where is the best place to tag it. Maybe we'd need to
first reorganize the content of site sources. Sg like:
ivy/site/ivy -> Ivy web site (currently in ivy/site)
ivy/site/ivyde -> IvyDE web site (as today)
ivy/site/xooki/trunk -> xooki version used in ivy sites
ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be used
for release branches documentation using an svn:externals

But I think it can wait for the next release (either of Ivy or IvyDE).




>
> And finally sent an announcement (after discussing it on the mailing list)

It sounds like a good plan.

Xavier

>
>
> Nicolas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

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

[Nicolas Lalevée]

Le mardi 1 juillet 2008, Xavier Hanin a écrit :

> On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée
> <nicolas.lalevee@...>
>
> wrote:
> > After one week of vote, here are the results:
> > 3 binding +1
> > 2 non binding +1
> >
> > The release is accepted !
>
> Great! Congratulations to the whole team and especially you, Nicolas!
>
> > So now I will push the binaries in dist.
> > I will regenerate entirely the ivyde website, which will include the
> > updatesite with its mirror configuration.
>
> That sounds nice.
>
> > I will tag the trunk branch (we talked about tagging xooki, but I don't
> > know where...? and actually I am reconsidering it as xooki is not
> > changing that much, is it really needed ?)
>
> We didn't tag it for Ivy releases, but it would be better to do it. But
> indeed I don't know where is the best place to tag it. Maybe we'd need to
> first reorganize the content of site sources. Sg like:
> ivy/site/ivy -> Ivy web site (currently in ivy/site)
> ivy/site/ivyde -> IvyDE web site (as today)
> ivy/site/xooki/trunk -> xooki version used in ivy sites
> ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be used
> for release branches documentation using an svn:externals
>
> But I think it can wait for the next release (either of Ivy or IvyDE).

I think so too.

So I have tagged, the binaries are publically available in dist. There is
still my pending question about the KEYS file:
About verifying the signatures, you will find mine there:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
But I am not sure how to update the KEYS file. I have found how to append my
public key:
(gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
But then should I just re-copy it into /www/www.apache.org/dist/ant/common on
people.apache.org ? There is no commit or whatever, right ?

I have regenerated the web site. For testing I have put it there:
http://ant.apache.org/ivy/ivyde.new/
There is an issue with the updatesite which I am currently fixing (at least
the mirrors setup is working :) ). But I have an issue with the download
page:
http://ant.apache.org/ivy/ivyde.new/download.html is not redirecting to the
cgi. And  
http://ant.apache.org/ivy/ivyde.new/download.cgi is redirecting me to
http://www.apache.org/dist/ .....
But the updatesite mirror configuration is working like a charm...
(http://ant.apache.org/ivy/ivyde.new/updatesite/eclipse-update--xml.cgi)

Any help will be appreciated.


Nicolas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Scheper, Erik-Berndt]

Hi,
 
I have tested the release and it seems to work fine for me. Thanks!
One comment however: the IVYDE Jira has not been updated (yet) to indicate this release.
 
Regards,
Erik-Berndt
 

________________________________

Van: Nicolas Lalevée [mailto:nicolas.lalevee@...]
Verzonden: di 1-7-2008 14:28
Aan: Ant Developers List
Onderwerp: Re: [Result] [VOTE] Release of Apache IvyDE 2.0.0.alpha1 (take 2)



Le mardi 1 juillet 2008, Xavier Hanin a écrit :

> On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée
> <nicolas.lalevee@...>
>
> wrote:
> > After one week of vote, here are the results:
> > 3 binding +1
> > 2 non binding +1
> >
> > The release is accepted !
>
> Great! Congratulations to the whole team and especially you, Nicolas!
>
> > So now I will push the binaries in dist.
> > I will regenerate entirely the ivyde website, which will include the
> > updatesite with its mirror configuration.
>
> That sounds nice.
>
> > I will tag the trunk branch (we talked about tagging xooki, but I don't
> > know where...? and actually I am reconsidering it as xooki is not
> > changing that much, is it really needed ?)
>
> We didn't tag it for Ivy releases, but it would be better to do it. But
> indeed I don't know where is the best place to tag it. Maybe we'd need to
> first reorganize the content of site sources. Sg like:
> ivy/site/ivy -> Ivy web site (currently in ivy/site)
> ivy/site/ivyde -> IvyDE web site (as today)
> ivy/site/xooki/trunk -> xooki version used in ivy sites
> ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be used
> for release branches documentation using an svn:externals
>
> But I think it can wait for the next release (either of Ivy or IvyDE).

I think so too.

So I have tagged, the binaries are publically available in dist. There is
still my pending question about the KEYS file:
About verifying the signatures, you will find mine there:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
But I am not sure how to update the KEYS file. I have found how to append my
public key:
(gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
But then should I just re-copy it into /www/www.apache.org/dist/ant/common on
people.apache.org ? There is no commit or whatever, right ?

I have regenerated the web site. For testing I have put it there:
http://ant.apache.org/ivy/ivyde.new/
There is an issue with the updatesite which I am currently fixing (at least
the mirrors setup is working :) ). But I have an issue with the download
page:
http://ant.apache.org/ivy/ivyde.new/download.html is not redirecting to the
cgi. And
http://ant.apache.org/ivy/ivyde.new/download.cgi is redirecting me to
http://www.apache.org/dist/ .....
But the updatesite mirror configuration is working like a charm...
(http://ant.apache.org/ivy/ivyde.new/updatesite/eclipse-update--xml.cgi)

Any help will be appreciated.


Nicolas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...




Disclaimer:
This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Nicolas Lalevée]

Le mardi 1 juillet 2008, Scheper, Erik-Berndt a écrit :
> Hi,
>
> I have tested the release and it seems to work fine for me. Thanks!
> One comment however: the IVYDE Jira has not been updated (yet) to indicate
> this release.

yeah, I missed that, thanks for raising it.

Nicolas

>
> Regards,
> Erik-Berndt
>
>
> ________________________________
>
> Van: Nicolas Lalevée [mailto:nicolas.lalevee@...]
> Verzonden: di 1-7-2008 14:28
> Aan: Ant Developers List
> Onderwerp: Re: [Result] [VOTE] Release of Apache IvyDE 2.0.0.alpha1 (take
> 2)
>
> Le mardi 1 juillet 2008, Xavier Hanin a écrit :
> > On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée
> > <nicolas.lalevee@...>
> >
> > wrote:
> > > After one week of vote, here are the results:
> > > 3 binding +1
> > > 2 non binding +1
> > >
> > > The release is accepted !
> >
> > Great! Congratulations to the whole team and especially you, Nicolas!
> >
> > > So now I will push the binaries in dist.
> > > I will regenerate entirely the ivyde website, which will include the
> > > updatesite with its mirror configuration.
> >
> > That sounds nice.
> >
> > > I will tag the trunk branch (we talked about tagging xooki, but I don't
> > > know where...? and actually I am reconsidering it as xooki is not
> > > changing that much, is it really needed ?)
> >
> > We didn't tag it for Ivy releases, but it would be better to do it. But
> > indeed I don't know where is the best place to tag it. Maybe we'd need to
> > first reorganize the content of site sources. Sg like:
> > ivy/site/ivy -> Ivy web site (currently in ivy/site)
> > ivy/site/ivyde -> IvyDE web site (as today)
> > ivy/site/xooki/trunk -> xooki version used in ivy sites
> > ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be used
> > for release branches documentation using an svn:externals
> >
> > But I think it can wait for the next release (either of Ivy or IvyDE).
>
> I think so too.
>
> So I have tagged, the binaries are publically available in dist. There is
> still my pending question about the KEYS file:
> About verifying the signatures, you will find mine there:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
> But I am not sure how to update the KEYS file. I have found how to append
> my public key:
> (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
> But then should I just re-copy it into /www/www.apache.org/dist/ant/common
> on people.apache.org ? There is no commit or whatever, right ?
>
> I have regenerated the web site. For testing I have put it there:
> http://ant.apache.org/ivy/ivyde.new/
> There is an issue with the updatesite which I am currently fixing (at least
> the mirrors setup is working :) ). But I have an issue with the download
> page:
> http://ant.apache.org/ivy/ivyde.new/download.html is not redirecting to the
> cgi. And
> http://ant.apache.org/ivy/ivyde.new/download.cgi is redirecting me to
> http://www.apache.org/dist/ .....
> But the updatesite mirror configuration is working like a charm...
> (http://ant.apache.org/ivy/ivyde.new/updatesite/eclipse-update--xml.cgi)
>
> Any help will be appreciated.
>
>
> Nicolas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>
>
> Disclaimer:
> This message contains information that may be privileged or confidential
> and is the property of Sogeti Nederland B.V. or its Group members. It is
> intended only for the person to whom it is addressed. If you are not the
> intended recipient, you are not authorized to read, print, retain, copy,
> disseminate, distribute, or use this message or any part thereof. If you
> receive this message in error, please notify the sender immediately and
> delete all copies of this message.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xavier Hanin]

On Tue, Jul 1, 2008 at 2:28 PM, Nicolas Lalevée <nicolas.lalevee@...>
wrote:

> Le mardi 1 juillet 2008, Xavier Hanin a écrit :
> > On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée
> > <nicolas.lalevee@...>
> >
> > wrote:
> > > After one week of vote, here are the results:
> > > 3 binding +1
> > > 2 non binding +1
> > >
> > > The release is accepted !
> >
> > Great! Congratulations to the whole team and especially you, Nicolas!
> >
> > > So now I will push the binaries in dist.
> > > I will regenerate entirely the ivyde website, which will include the
> > > updatesite with its mirror configuration.
> >
> > That sounds nice.
> >
> > > I will tag the trunk branch (we talked about tagging xooki, but I don't
> > > know where...? and actually I am reconsidering it as xooki is not
> > > changing that much, is it really needed ?)
> >
> > We didn't tag it for Ivy releases, but it would be better to do it. But
> > indeed I don't know where is the best place to tag it. Maybe we'd need to
> > first reorganize the content of site sources. Sg like:
> > ivy/site/ivy -> Ivy web site (currently in ivy/site)
> > ivy/site/ivyde -> IvyDE web site (as today)
> > ivy/site/xooki/trunk -> xooki version used in ivy sites
> > ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be used
> > for release branches documentation using an svn:externals
> >
> > But I think it can wait for the next release (either of Ivy or IvyDE).
>
> I think so too.
>
> So I have tagged, the binaries are publically available in dist. There is
> still my pending question about the KEYS file:
> About verifying the signatures, you will find mine there:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
> But I am not sure how to update the KEYS file. I have found how to append
> my
> public key:
> (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
> But then should I just re-copy it into /www/www.apache.org/dist/ant/commonon
> people.apache.org ? There is no commit or whatever, right ?
>
> I have regenerated the web site. For testing I have put it there:
> http://ant.apache.org/ivy/ivyde.new/
> There is an issue with the updatesite which I am currently fixing (at least
> the mirrors setup is working :) ). But I have an issue with the download
> page:
> http://ant.apache.org/ivy/ivyde.new/download.html is not redirecting to
> the
> cgi.

This is because you need to include download-redirect.js script. I've fixed
it in svn.

> And
> http://ant.apache.org/ivy/ivyde.new/download.cgi is redirecting me to
> http://www.apache.org/dist/ .....

This is strange, I've checked the download.cgi on people.a.o and it seems
fine. I've however made some changes in svn: set svn:eol-style and
svn:executable properties, and removed the end of line at the end of the
file to make it the exact copy of the download.cgi  we have in Ivy site. I
suggest you update ivyde.new with the current target/ivyde site in svn and
see if it works better.

BTW, since svn:eol-style is missing on files you added in svn, I'm wondering
if you have configured your svn client as suggested here:
http://www.apache.org/dev/version-control.html

If you haven't already, I think it would be nice to do.

Xavier

> But the updatesite mirror configuration is working like a charm...
> (http://ant.apache.org/ivy/ivyde.new/updatesite/eclipse-update--xml.cgi)
>
> Any help will be appreciated.
>
>
> Nicolas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

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

[Xavier Hanin]

On Tue, Jul 1, 2008 at 2:28 PM, Nicolas Lalevée <nicolas.lalevee@...>
wrote:

>
> So I have tagged, the binaries are publically available in dist. There is
> still my pending question about the KEYS file:
> About verifying the signatures, you will find mine there:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
> But I am not sure how to update the KEYS file. I have found how to append
> my
> public key:
> (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
> But then should I just re-copy it into /www/www.apache.org/dist/ant/commonon
> people.apache.org ? There is no commit or whatever, right ?

Sorry for the late reply, I didn't recall myself what we do for keys, but
I've found back Stefan's tip when I released Ivy. The KEYS file to update is
in svn, here:
https://svn.apache.org/repos/asf/ant/core/trunk/KEYS

Update this file, commit, and if I understand correctly the online
version<http://www.apache.org/dist/ant/KEYS>will be updated
automatically.

Xavier

[Xavier Hanin]

On Wed, Jul 2, 2008 at 10:59 AM, Xavier Hanin <xavier.hanin@...>
wrote:

> On Tue, Jul 1, 2008 at 2:28 PM, Nicolas Lalevée <
> nicolas.lalevee@...> wrote:
>
>> Le mardi 1 juillet 2008, Xavier Hanin a écrit :
>> > On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée
>> > <nicolas.lalevee@...>
>> >
>> > wrote:
>> > > After one week of vote, here are the results:
>> > > 3 binding +1
>> > > 2 non binding +1
>> > >
>> > > The release is accepted !
>> >
>> > Great! Congratulations to the whole team and especially you, Nicolas!
>> >
>> > > So now I will push the binaries in dist.
>> > > I will regenerate entirely the ivyde website, which will include the
>> > > updatesite with its mirror configuration.
>> >
>> > That sounds nice.
>> >
>> > > I will tag the trunk branch (we talked about tagging xooki, but I
>> don't
>> > > know where...? and actually I am reconsidering it as xooki is not
>> > > changing that much, is it really needed ?)
>> >
>> > We didn't tag it for Ivy releases, but it would be better to do it. But
>> > indeed I don't know where is the best place to tag it. Maybe we'd need
>> to
>> > first reorganize the content of site sources. Sg like:
>> > ivy/site/ivy -> Ivy web site (currently in ivy/site)
>> > ivy/site/ivyde -> IvyDE web site (as today)
>> > ivy/site/xooki/trunk -> xooki version used in ivy sites
>> > ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be
>> used
>> > for release branches documentation using an svn:externals
>> >
>> > But I think it can wait for the next release (either of Ivy or IvyDE).
>>
>> I think so too.
>>
>> So I have tagged, the binaries are publically available in dist. There is
>> still my pending question about the KEYS file:
>> About verifying the signatures, you will find mine there:
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
>> But I am not sure how to update the KEYS file. I have found how to append
>> my
>> public key:
>> (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
>> But then should I just re-copy it into /www/
>> www.apache.org/dist/ant/common on
>> people.apache.org ? There is no commit or whatever, right ?
>>
>> I have regenerated the web site. For testing I have put it there:
>> http://ant.apache.org/ivy/ivyde.new/
>> There is an issue with the updatesite which I am currently fixing (at
>> least
>> the mirrors setup is working :) ). But I have an issue with the download
>> page:
>> http://ant.apache.org/ivy/ivyde.new/download.html is not redirecting to
>> the
>> cgi.
>
> This is because you need to include download-redirect.js script. I've fixed
> it in svn.
>
>> And
>> http://ant.apache.org/ivy/ivyde.new/download.cgi is redirecting me to
>> http://www.apache.org/dist/ .....
>
> This is strange, I've checked the download.cgi on people.a.o and it seems
> fine. I've however made some changes in svn: set svn:eol-style and
> svn:executable properties, and removed the end of line at the end of the
> file to make it the exact copy of the download.cgi  we have in Ivy site. I
> suggest you update ivyde.new with the current target/ivyde site in svn and
> see if it works better.
>

While wanting to update Ivy site to reflect the change for wiki link, I
forgot it updates ivyde site too... Hence I've updated IvyDE site with the
changes you were testing in ivyde.new. I think we can keep it like that,
hopefully we'll soon find the trick to get download.cgi fixed.

Xavier

>
> BTW, since svn:eol-style is missing on files you added in svn, I'm
> wondering if you have configured your svn client as suggested here:
> http://www.apache.org/dev/version-control.html
>
> If you haven't already, I think it would be nice to do.
>
> Xavier
>
>
>> But the updatesite mirror configuration is working like a charm...
>> (http://ant.apache.org/ivy/ivyde.new/updatesite/eclipse-update--xml.cgi)
>>
>> Any help will be appreciated.
>>
>>
>> Nicolas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>
>
> --
> 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]

On Wed, Jul 2, 2008 at 12:07 PM, Xavier Hanin <xavier.hanin@...>
wrote:

>
> While wanting to update Ivy site to reflect the change for wiki link, I
> forgot it updates ivyde site too... Hence I've updated IvyDE site with the
> changes you were testing in ivyde.new. I think we can keep it like that,
> hopefully we'll soon find the trick to get download.cgi fixed.
>

The site has been updated, download.html redirects to download.cgi, but we
still get redirected to http://www.apache.org/dist/

Looking back at the problems I had when I set up download.cgi for Ivy, I've
removed the square brackets used in download.html content, because it's a
source of problem for the python mirror script. But last time I faced this
problem of square brackets I got HTTP 500 errors, not a redirection to
http://www.apache.org/dist/. So I don't know if it will be fixed with that
or know, we have to wait for the site to be synced from minotaur to public.


Xavier

[Nicolas Lalevée]

Le mercredi 2 juillet 2008, Xavier Hanin a écrit :
> On Wed, Jul 2, 2008 at 12:07 PM, Xavier Hanin <xavier.hanin@...>
>
> wrote:
> > While wanting to update Ivy site to reflect the change for wiki link, I
> > forgot it updates ivyde site too... Hence I've updated IvyDE site with
> > the changes you were testing in ivyde.new. I think we can keep it like
> > that, hopefully we'll soon find the trick to get download.cgi fixed.

ok, it is by the way nearly ready to be deployed.

but then could you grant the ant group some write permission please ?
I have still some fixes to do on the updatesite

> The site has been updated, download.html redirects to download.cgi, but we
> still get redirected to http://www.apache.org/dist/
>
> Looking back at the problems I had when I set up download.cgi for Ivy, I've
> removed the square brackets used in download.html content, because it's a
> source of problem for the python mirror script. But last time I faced this
> problem of square brackets I got HTTP 500 errors, not a redirection to
> http://www.apache.org/dist/. So I don't know if it will be fixed with that
> or know, we have to wait for the site to be synced from minotaur to public.

ok, thanks for the fix and having a look to it.

Nicolas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Nicolas Lalevée]

Le mercredi 2 juillet 2008, Xavier Hanin a écrit :

> On Tue, Jul 1, 2008 at 2:28 PM, Nicolas Lalevée
> <nicolas.lalevee@...>
>
> wrote:
> > Le mardi 1 juillet 2008, Xavier Hanin a écrit :
> > > On Mon, Jun 30, 2008 at 7:18 PM, Nicolas Lalevée
> > > <nicolas.lalevee@...>
> > >
> > > wrote:
> > > > After one week of vote, here are the results:
> > > > 3 binding +1
> > > > 2 non binding +1
> > > >
> > > > The release is accepted !
> > >
> > > Great! Congratulations to the whole team and especially you, Nicolas!
> > >
> > > > So now I will push the binaries in dist.
> > > > I will regenerate entirely the ivyde website, which will include the
> > > > updatesite with its mirror configuration.
> > >
> > > That sounds nice.
> > >
> > > > I will tag the trunk branch (we talked about tagging xooki, but I
> > > > don't know where...? and actually I am reconsidering it as xooki is
> > > > not changing that much, is it really needed ?)
> > >
> > > We didn't tag it for Ivy releases, but it would be better to do it. But
> > > indeed I don't know where is the best place to tag it. Maybe we'd need
> > > to first reorganize the content of site sources. Sg like:
> > > ivy/site/ivy -> Ivy web site (currently in ivy/site)
> > > ivy/site/ivyde -> IvyDE web site (as today)
> > > ivy/site/xooki/trunk -> xooki version used in ivy sites
> > > ivy/site/xooki/tags/xxx -> tagged versions of xooki, which should be
> > > used for release branches documentation using an svn:externals
> > >
> > > But I think it can wait for the next release (either of Ivy or IvyDE).
> >
> > I think so too.
> >
> > So I have tagged, the binaries are publically available in dist. There is
> > still my pending question about the KEYS file:
> > About verifying the signatures, you will find mine there:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
> > But I am not sure how to update the KEYS file. I have found how to append
> > my
> > public key:
> > (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
> > But then should I just re-copy it into
> > /www/www.apache.org/dist/ant/commonon people.apache.org ? There is no
> > commit or whatever, right ?
> >
> > I have regenerated the web site. For testing I have put it there:
> > http://ant.apache.org/ivy/ivyde.new/
> > There is an issue with the updatesite which I am currently fixing (at
> > least the mirrors setup is working :) ). But I have an issue with the
> > download page:
> > http://ant.apache.org/ivy/ivyde.new/download.html is not redirecting to
> > the
> > cgi.
>
> This is because you need to include download-redirect.js script. I've fixed
> it in svn.
>
> > And
> > http://ant.apache.org/ivy/ivyde.new/download.cgi is redirecting me to
> > http://www.apache.org/dist/ .....
>
> This is strange, I've checked the download.cgi on people.a.o and it seems
> fine. I've however made some changes in svn: set svn:eol-style and
> svn:executable properties, and removed the end of line at the end of the
> file to make it the exact copy of the download.cgi  we have in Ivy site. I
> suggest you update ivyde.new with the current target/ivyde site in svn and
> see if it works better.
>
> BTW, since svn:eol-style is missing on files you added in svn, I'm
> wondering if you have configured your svn client as suggested here:
> http://www.apache.org/dev/version-control.html
>
> If you haven't already, I think it would be nice to do.

Actually I did, but not on the machine I used to deploy the web site :p
I will fix that.

Nicolas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xavier Hanin]

On Wed, Jul 2, 2008 at 3:57 PM, Nicolas Lalevée <nicolas.lalevee@...>
wrote:

> Le mercredi 2 juillet 2008, Xavier Hanin a écrit :
> > On Wed, Jul 2, 2008 at 12:07 PM, Xavier Hanin <xavier.hanin@...>
> >
> > wrote:
> > > While wanting to update Ivy site to reflect the change for wiki link, I
> > > forgot it updates ivyde site too... Hence I've updated IvyDE site with
> > > the changes you were testing in ivyde.new. I think we can keep it like
> > > that, hopefully we'll soon find the trick to get download.cgi fixed.
>
> ok, it is by the way nearly ready to be deployed.
>
> but then could you grant the ant group some write permission please ?

I've updated the permissions, sorry about that, I don't know why my umask is
not used when I do the svn up...

Xavier

>
> I have still some fixes to do on the updatesite
>
> > The site has been updated, download.html redirects to download.cgi, but
> we
> > still get redirected to http://www.apache.org/dist/
> >
> > Looking back at the problems I had when I set up download.cgi for Ivy,
> I've
> > removed the square brackets used in download.html content, because it's a
> > source of problem for the python mirror script. But last time I faced
> this
> > problem of square brackets I got HTTP 500 errors, not a redirection to
> > http://www.apache.org/dist/. So I don't know if it will be fixed with
> that
> > or know, we have to wait for the site to be synced from minotaur to
> public.
>
> ok, thanks for the fix and having a look to it.
>
> Nicolas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

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

[Xavier Hanin]

On Wed, Jul 2, 2008 at 1:51 PM, Xavier Hanin <xavier.hanin@...> wrote:

> On Wed, Jul 2, 2008 at 12:07 PM, Xavier Hanin <xavier.hanin@...>
> wrote:
>
>>
>> While wanting to update Ivy site to reflect the change for wiki link, I
>> forgot it updates ivyde site too... Hence I've updated IvyDE site with the
>> changes you were testing in ivyde.new. I think we can keep it like that,
>> hopefully we'll soon find the trick to get download.cgi fixed.
>>
>
> The site has been updated, download.html redirects to download.cgi, but we
> still get redirected to http://www.apache.org/dist/
>
> Looking back at the problems I had when I set up download.cgi for Ivy, I've
> removed the square brackets used in download.html content, because it's a
> source of problem for the python mirror script. But last time I faced this
> problem of square brackets I got HTTP 500 errors, not a redirection to
> http://www.apache.org/dist/. So I don't know if it will be fixed with that
> or know, we have to wait for the site to be synced from minotaur to public.

download page appears to be working now, so it seems removing the square
brackets in download.html was the last trick to make it work.

Hence, for the record, to get download.cgi working we need:
- to make it executable on the unix filesystem on minotaur, which is
achieved with the svn:executable property
- to make sure that it contains only unix EOL, which can be achieved using
the svn:eol-style native property
- to make sure that the download.html doesn't contain any square bracket but
the one used by the mirror script itself (like [preferred], ...)

And to redirect download.html to download.cgi, we just need to include the
download-redirect.js script in download.html

Xavier


>
>
>
> Xavier




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

[Nicolas Lalevée]

Le mercredi 2 juillet 2008, Xavier Hanin a écrit :

> On Tue, Jul 1, 2008 at 2:28 PM, Nicolas Lalevée
> <nicolas.lalevee@...>
>
> wrote:
> > So I have tagged, the binaries are publically available in dist. There is
> > still my pending question about the KEYS file:
> > About verifying the signatures, you will find mine there:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
> > But I am not sure how to update the KEYS file. I have found how to append
> > my
> > public key:
> > (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
> > But then should I just re-copy it into
> > /www/www.apache.org/dist/ant/commonon people.apache.org ? There is no
> > commit or whatever, right ?
>
> Sorry for the late reply, I didn't recall myself what we do for keys, but
> I've found back Stefan's tip when I released Ivy. The KEYS file to update
> is in svn, here:
> https://svn.apache.org/repos/asf/ant/core/trunk/KEYS
>
> Update this file, commit, and if I understand correctly the online
> version<http://www.apache.org/dist/ant/KEYS>will be updated
> automatically.

I have updated https://svn.apache.org/repos/asf/ant/core/trunk/KEYS
But it didn't get updated.
Then I wanted to update it manually and I have found that this file
http://www.apache.org/dist/ant/KEYS is actually corresponding to this file in
svn:
https://svn.apache.org/repos/asf/ant/antlibs/common/trunk/KEYS

should I update this one too ?

Nicolas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...