You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Peter Firmstone <ji...@zeus.net.au> on 2009/04/03 13:47:14 UTC
Migration to Java 5 - Summary
Just thought I'd go back over the messages and post a summary:
Those in favour of using Java 6 features:
Jeremy Easton-Marks
Greg Wonderly
James Grahn
Those in favour of using Java 5 features:
Dennis Reedy
Jim Waldo
Jonathan Costers
Greg Trasuk
Niclas Hedhman
Dan Rollo
Greg Wonderly
Jukka Zitting
Sean Landis
Peter Firmstone
James Grahn
Those who would like to see continued support for JRE 1.4 (bytecode
only, using Retrotranslator):
Patrick Wright
Greg Trasuk
Wade Chandler
Peter Firmstone
I propose posting the following items on Jira:
1. Migration to Java 5 Language Features and API
2. Use of Generics in JavaSpace API, as suggested by James Grahn.
3. Implementation of Retrotranslator for JRE 1.4 Runtime support.
Best Regards,
Peter Firmstone.
Gregg Wonderly wrote:
> James Grahn wrote:
>> Actually, Gregg, what I had in mind was this:
>>
>> public <T extends Entry> T read(T template, Transaction txn, long
>> timeout)
>
> I always forget about that very handy way to restrict parameters and
> return values to the same type. That will be a useful way to help
> manage that the types are in the right hierarchy.
>
> Gregg Wonderly
>
RE: Migration to Java 5 - Summary
Posted by Tom Hobbs <to...@sucfin.com>.
Hi all,
This makes perfect sense to me. Before we start thinking up more ways
to release AR2 lets take what we have and get it out - if nothing else
it proves that there's still life in this project! :-)
I'd also be tempted to call the package name changes and the move to
Java[56] it for release 3.0. Both of those are big changes which will
have big impacts on users existing code bases without adding more to the
mix.
> We are looking forward to contributions from interested people.
What's the process for supplying extra documentation? Are Jiras
raised/commented on or is it something else? Here I'm thinking of the
wiki and editing rights.
Cheers,
Tom
-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com]
Sent: 03 April 2009 13:19
To: river-dev@incubator.apache.org
Subject: Re: Migration to Java 5 - Summary
Hi,
On Fri, Apr 3, 2009 at 2:06 PM, Jeremy Easton-Marks
<co...@gmail.com> wrote:
> When are we proposing to make these changes? This release? A future
point
> release? Or River 3.X?
I'm thinking about cutting AR2 fairly soon as the test integration
that I was worried about earlier has been progressing very well.
After that I'd propose that we do the package mapping to
org.apache.river and upgrade to Java 5. The release numbering should
bump to Apache River 3.0 to indicate these changes.
> On a completely different point. What are we doing about
documentation,
> examples, and other things of that nature?
We are looking forward to contributions from interested people. :-)
BR,
Jukka Zitting
www.sucden.co.uk
Sucden (UK) Limited, 5 London Bridge Street, London SE1 9SG
Telephone +44 20 7940 9400
Registered in England no. 1095841
VAT registration no. GB 446 9061 33
Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA register under no. 114239
This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify postmaster@sucden.co.uk immediately and delete it from your computer system.
We believe, but do not warrant, that this email and its attachments are virus-free, but you should check.
Sucden (UK) Ltd may monitor traffic data of both business and personal emails. By replying to this email, you consent to Sucden’s monitoring the content of any emails you send to or receive from Sucden. Sucden is not liable for any opinions expressed by the sender where this is a non-business email.
The contents of this e-mail do not constitute advice and should not be regarded as a recommendation to buy, sell or otherwise deal with any particular investment.
This message has been scanned for viruses by Mimecast.
Re: Migration to Java 5 - Summary
Posted by Peter Firmstone <ji...@zeus.net.au>.
Agree +1
Peter Firmstone.
Jukka Zitting wrote:
> Hi,
>
> On Fri, Apr 3, 2009 at 2:06 PM, Jeremy Easton-Marks
> <co...@gmail.com> wrote:
>
>> When are we proposing to make these changes? This release? A future point
>> release? Or River 3.X?
>>
>
> I'm thinking about cutting AR2 fairly soon as the test integration
> that I was worried about earlier has been progressing very well.
>
> After that I'd propose that we do the package mapping to
> org.apache.river and upgrade to Java 5. The release numbering should
> bump to Apache River 3.0 to indicate these changes.
>
>
>> On a completely different point. What are we doing about documentation,
>> examples, and other things of that nature?
>>
>
> We are looking forward to contributions from interested people. :-)
>
> BR,
>
> Jukka Zitting
>
>
Re: Migration to Java 5 - Summary
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Apr 3, 2009 at 2:06 PM, Jeremy Easton-Marks
<co...@gmail.com> wrote:
> When are we proposing to make these changes? This release? A future point
> release? Or River 3.X?
I'm thinking about cutting AR2 fairly soon as the test integration
that I was worried about earlier has been progressing very well.
After that I'd propose that we do the package mapping to
org.apache.river and upgrade to Java 5. The release numbering should
bump to Apache River 3.0 to indicate these changes.
> On a completely different point. What are we doing about documentation,
> examples, and other things of that nature?
We are looking forward to contributions from interested people. :-)
BR,
Jukka Zitting
Re: Migration to Java 5 - Summary
Posted by Jeremy Easton-Marks <co...@gmail.com>.
When are we proposing to make these changes? This release? A future point
release? Or River 3.X?
I think we should continue to work in 1.4 for this release unless anyone
sees any immediate need for it. I am personally going to have difficulty
selling the idea to my boss to use River if progress towards a full release
out of hibernation is not done.
Since upgrading to 1.5 or 1.6 can significantly change out code base I think
it would be best to wait for the next major release. At that point we can
use a minimum of 1.5 and possible 1.6.
On a completely different point. What are we doing about documentation,
examples, and other things of that nature?
Jeremy R. Easton-Marks
"être fort pour être utile"
On Fri, Apr 3, 2009 at 6:47 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> Just thought I'd go back over the messages and post a summary:
>
> Those in favour of using Java 6 features:
>
> Jeremy Easton-Marks
> Greg Wonderly
> James Grahn
>
> Those in favour of using Java 5 features:
>
> Dennis Reedy
> Jim Waldo
> Jonathan Costers
> Greg Trasuk
> Niclas Hedhman
> Dan Rollo
> Greg Wonderly
> Jukka Zitting
> Sean Landis
> Peter Firmstone
> James Grahn
>
>
> Those who would like to see continued support for JRE 1.4 (bytecode only,
> using Retrotranslator):
>
> Patrick Wright
> Greg Trasuk
> Wade Chandler
> Peter Firmstone
>
>
> I propose posting the following items on Jira:
>
> 1. Migration to Java 5 Language Features and API
> 2. Use of Generics in JavaSpace API, as suggested by James Grahn.
> 3. Implementation of Retrotranslator for JRE 1.4 Runtime support.
>
> Best Regards,
>
> Peter Firmstone.
>
> Gregg Wonderly wrote:
>
>> James Grahn wrote:
>>
>>> Actually, Gregg, what I had in mind was this:
>>>
>>> public <T extends Entry> T read(T template, Transaction txn, long
>>> timeout)
>>>
>>
>> I always forget about that very handy way to restrict parameters and
>> return values to the same type. That will be a useful way to help manage
>> that the types are in the right hierarchy.
>>
>> Gregg Wonderly
>>
>>
>
>
Re: Migration to Java 5 - Summary
Posted by Greg Trasuk <tr...@stratuscom.com>.
On Fri, 2009-04-03 at 07:47, Peter Firmstone wrote:
> Just thought I'd go back over the messages and post a summary:
>
> Those in favour of using Java 6 features:
>
> Jeremy Easton-Marks
> Greg Wonderly
> James Grahn
>
> Those in favour of using Java 5 features:
>
> Dennis Reedy
> Jim Waldo
> Jonathan Costers
> Greg Trasuk
> Niclas Hedhman
> Dan Rollo
> Greg Wonderly
> Jukka Zitting
> Sean Landis
> Peter Firmstone
> James Grahn
>
>
> Those who would like to see continued support for JRE 1.4 (bytecode
> only, using Retrotranslator):
>
> Patrick Wright
> Greg Trasuk
I'm not in favour of using Retro-anything. I don't see the use case,
and I get very nervous when people talk about back-porting stuff from
Harmony's 1.5 implementation.
Move on to Java 1.5 and be done with it.
Greg Trasuk
> Wade Chandler
> Peter Firmstone
>
>
> I propose posting the following items on Jira:
>
> 1. Migration to Java 5 Language Features and API
> 2. Use of Generics in JavaSpace API, as suggested by James Grahn.
> 3. Implementation of Retrotranslator for JRE 1.4 Runtime support.
>
> Best Regards,
>
> Peter Firmstone.
>
> Gregg Wonderly wrote:
> > James Grahn wrote:
> >> Actually, Gregg, what I had in mind was this:
> >>
> >> public <T extends Entry> T read(T template, Transaction txn, long
> >> timeout)
> >
> > I always forget about that very handy way to restrict parameters and
> > return values to the same type. That will be a useful way to help
> > manage that the types are in the right hierarchy.
> >
> > Gregg Wonderly
> >
--
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.com