You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@apache.org> on 2006/11/16 13:11:55 UTC
[Vote] Use latest rhino in 2.1.x
Ok, it seems we should vote on this topic. As you all know,
including the version of rhino in 2.1.x has legal problems
and we have to do something about it.
Fortunately, the latest version of Rhino is licenced under an acceptable
term, so we could include that version in 2.1.x. Unfortunately this
creates minor incompatibilites and might infect people using specific
functions in flowscript. On the other hand, if we insist on using the
current version we can't include rhino in our releases, split out the
flow stuff from core, make it available separately, force people to
download it and download rhino from somewhere else...and so on. So in
the end we have to decide which solution hurts less for our users.
It seems that we think that using the latest version of rhino is less
pain, so let's vote on this.
Please cast your votes for using latest rhino in 2.1.x.
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [Vote] Use latest rhino in 2.1.x
Posted by Jeremy Quinn <je...@apache.org>.
On 16 Nov 2006, at 12:22, Bertrand Delacretaz wrote:
> On 11/16/06, Carsten Ziegeler <cz...@apache.org> wrote:
>
>> ...Please cast your votes for using latest rhino in 2.1.x...
ditto, my +1
regards Jeremy
Re: [Vote] Use latest rhino in 2.1.x
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 11/16/06, Carsten Ziegeler <cz...@apache.org> wrote:
> ...Please cast your votes for using latest rhino in 2.1.x...
+1
-Bertrand
Re: [Vote] Use latest rhino in 2.1.x
Posted by Carsten Ziegeler <cz...@apache.org>.
Bruno Dumon wrote:
> Hi,
>
> This vote passed with lots of +1 and no -1.
>
> Just in case anyone is working on the same: I could look into doing the
> upgrade tomorrow.
>
Go ahead :) Thanks Bruno
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [Vote] Use latest rhino in 2.1.x
Posted by Bruno Dumon <br...@outerthought.org>.
Hi,
This vote passed with lots of +1 and no -1.
Just in case anyone is working on the same: I could look into doing the
upgrade tomorrow.
On Thu, 2006-11-16 at 13:11 +0100, Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
>
> Carsten
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
Re: [Vote] Use latest rhino in 2.1.x
Posted by Andreas Hochsteger <an...@gmail.com>.
2006/11/16, Carsten Ziegeler <cz...@apache.org>:
>
> Please cast your votes for using latest rhino in 2.1.x.
>
+1
--
Andreas
Re: [Vote] Use latest rhino in 2.1.x
Posted by Daniel Fagerstrom <da...@nada.kth.se>.
Carsten Ziegeler skrev:
...
> Please cast your votes for using latest rhino in 2.1.x.
>
+1
/Daniel
Re: [Vote] Use latest rhino in 2.1.x
Posted by Reinhard Poetz <re...@apache.org>.
Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
+1
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [Vote] Use latest rhino in 2.1.x
Posted by Ralph Goers <Ra...@dslextreme.com>.
+1
Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
>
> Carsten
>
Re: [Vote] Use latest rhino in 2.1.x
Posted by Sylvain Wallez <sy...@apache.org>.
Carsten Ziegeler wrote:
> Please cast your votes for using latest rhino in 2.1.x.
>
+1
Sylvain
--
Sylvain Wallez - http://bluxte.net
Re: [Vote] Use latest rhino in 2.1.x
Posted by Jason Johnston <co...@lojjic.net>.
Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
+1.
Re: [Vote] Use latest rhino in 2.1.x
Posted by Peter Hunsberger <pe...@gmail.com>.
On 11/16/06, Carsten Ziegeler <cz...@apache.org> wrote:
> Please cast your votes for using latest rhino in 2.1.x.
+1 - we're pretty dependant on the current implementation of flow but
I can't imagine that anythign will break that we can't easily fix.
--
Peter Hunsberger
Re: [Vote] Use latest rhino in 2.1.x
Posted by Andrew Savory <an...@luminas.co.uk>.
Hi,
On 16 Nov 2006, at 12:11, Carsten Ziegeler wrote:
> Please cast your votes for using latest rhino in 2.1.x.
+1
Thanks,
Andrew.
--
Andrew Savory, Managing Director, Luminas Limited
Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135
Web: http://www.luminas.co.uk/
Sourcesense: http://www.sourcesense.com/
Re: [Vote] Use latest rhino in 2.1.x
Posted by Bruno Dumon <br...@outerthought.org>.
On Thu, 2006-11-16 at 13:11 +0100, Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
+1
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
Re: [Vote] Use latest rhino in 2.1.x
Posted by Carsten Ziegeler <cz...@apache.org>.
>
> Please cast your votes for using latest rhino in 2.1.x.
>
+1
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [Vote] Use latest rhino in 2.1.x
Posted by Jorg Heymans <jh...@apache.org>.
Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
>
> Carsten
+1
Jorg
Re: [Vote] Use latest rhino in 2.1.x
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Sylvain Wallez wrote:
> Leszek Gawron wrote:
>> Carsten Ziegeler wrote:
>>
>>> Ok, it seems we should vote on this topic. As you all know,
>>> including the version of rhino in 2.1.x has legal problems
>>> and we have to do something about it.
>>>
>>> Fortunately, the latest version of Rhino is licenced under an acceptable
>>> term, so we could include that version in 2.1.x. Unfortunately this
>>> creates minor incompatibilites and might infect people using specific
>>> functions in flowscript. On the other hand, if we insist on using the
>>>
>> which are?
>>
>
> The special exception constructs to catch continuation suspend and
> restore, that can be used to cleanup or restore non-suspendable resources.
>
> try {
> // code...
> } catch(break) {
> // continuation suspended
> } catch(continue) {
> // continuation restored
> }
AFAIU from the thread provided there is a replacement using finally
keyword. I'm fine with that.
--
Leszek Gawron CTO at MobileBox Ltd.
Re: [Vote] Use latest rhino in 2.1.x
Posted by Sylvain Wallez <sy...@apache.org>.
Leszek Gawron wrote:
> Carsten Ziegeler wrote:
>
>> Ok, it seems we should vote on this topic. As you all know,
>> including the version of rhino in 2.1.x has legal problems
>> and we have to do something about it.
>>
>> Fortunately, the latest version of Rhino is licenced under an acceptable
>> term, so we could include that version in 2.1.x. Unfortunately this
>> creates minor incompatibilites and might infect people using specific
>> functions in flowscript. On the other hand, if we insist on using the
>>
>
> which are?
>
The special exception constructs to catch continuation suspend and
restore, that can be used to cleanup or restore non-suspendable resources.
try {
// code...
} catch(break) {
// continuation suspended
} catch(continue) {
// continuation restored
}
Sylvain
--
Sylvain Wallez - http://bluxte.net
Re: [Vote] Use latest rhino in 2.1.x
Posted by Carsten Ziegeler <cz...@apache.org>.
Leszek Gawron wrote:
> Carsten Ziegeler wrote:
>> Ok, it seems we should vote on this topic. As you all know,
>> including the version of rhino in 2.1.x has legal problems
>> and we have to do something about it.
>>
>> Fortunately, the latest version of Rhino is licenced under an acceptable
>> term, so we could include that version in 2.1.x. Unfortunately this
>> creates minor incompatibilites and might infect people using specific
>> functions in flowscript. On the other hand, if we insist on using the
>
> which are?
See this thread for more info:
http://marc.theaimsgroup.com/?t=116195321200002&r=1&w=2
Let's please not discuss the problems in this vote thread - if there is
need to discuss, let's do it in the thread mentioned above.
Carsten
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [Vote] Use latest rhino in 2.1.x
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
which are?
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
>
> Carsten
--
Leszek Gawron CTO at MobileBox Ltd.
Re: [Vote] Use latest rhino in 2.1.x
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Carsten Ziegeler wrote:
> Please cast your votes for using latest rhino in 2.1.x.
+1
Vadim
Re: [Vote] Use latest rhino in 2.1.x
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Carsten Ziegeler wrote:
> Ok, it seems we should vote on this topic. As you all know,
> including the version of rhino in 2.1.x has legal problems
> and we have to do something about it.
>
> Fortunately, the latest version of Rhino is licenced under an acceptable
> term, so we could include that version in 2.1.x. Unfortunately this
> creates minor incompatibilites and might infect people using specific
> functions in flowscript. On the other hand, if we insist on using the
> current version we can't include rhino in our releases, split out the
> flow stuff from core, make it available separately, force people to
> download it and download rhino from somewhere else...and so on. So in
> the end we have to decide which solution hurts less for our users.
> It seems that we think that using the latest version of rhino is less
> pain, so let's vote on this.
>
> Please cast your votes for using latest rhino in 2.1.x.
+1
--
Leszek Gawron CTO at MobileBox Ltd.
Re: [Vote] Use latest rhino in 2.1.x
Posted by Joerg Heinicke <jo...@gmx.de>.
On 16.11.2006 13:11, Carsten Ziegeler wrote:
> Please cast your votes for using latest rhino in 2.1.x.
+1
Jörg
Re: [Vote] Use latest rhino in 2.1.x
Posted by Giacomo Pati <gi...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Carsten Ziegeler wrote:
> Please cast your votes for using latest rhino in 2.1.x.
+1
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFXLGrLNdJvZjjVZARAjtnAJ4vf4d1ZCj94cPKr6ERl+Pl4t5JGwCcDgoF
XwqEO0vjOampUW9UQrPPn+U=
=8n/e
-----END PGP SIGNATURE-----