You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Steve Vinoski <vi...@iona.com> on 2006/09/08 23:53:40 UTC

which Java version?

Does Qpid mandate Java 5? The reason I ask is that I had some code  
checking turned on in my maven work and saw a ton of warnings about  
unchecked calls to collections classes. If we mandate 1.5, should we  
turn on such checking so we can make the code cleaner?

--steve

[java] Re: which Java version?

Posted by Gordon Sim <gs...@redhat.com>.
I agree we should make a firm decision and either enforce 1.4 or fully 
exploit 1.5. Originally the client was developed with a view to 
supporting 1.4 - I *believe* that it may now have one or two small 
dependencies on 1.5 though I can't be sure that I remember correctly.

Steve Vinoski wrote:
> Hi Carl, I feel like we need to nail this down firmer than that. If we 
> want to support clients at 1.4, for example, then that's a stake in the 
> ground that has to be enforced by all qpid developers as it has a 
> variety of implications on the implementation. We'd have to make sure 
> that any parts of the code required for clients always remained at 1.4 
> and used only 1.4-compatible versions of underlying libraries, which 
> implies that the qpid common code all has to be 1.4 as well.
> 
> Personally, I think we should just say 1.5 across the board.
> 
> --steve
> 
> On Sep 8, 2006, at 6:27 PM, Carl Trieloff wrote:
> 
>>
>> Java 1.5 or 1.6 for broker.
>>
>> For clients 1.4 might be good to also support.
>>
>> Carl.
>>
>> Steve Vinoski wrote:
>>> Does Qpid mandate Java 5? The reason I ask is that I had some code 
>>> checking turned on in my maven work and saw a ton of warnings about 
>>> unchecked calls to collections classes. If we mandate 1.5, should we 
>>> turn on such checking so we can make the code cleaner?
>>>
>>> --steve
>>
> 


Re: which Java version?

Posted by ma...@jpmorgan.com.
I'm in favour of simply stating support for 1.5 too.

Regards,
Marnie






Steve Vinoski <vi...@iona.com>
10/09/2006 02:13
Please respond to qpid-dev
 
        To:     qpid-dev@incubator.apache.org
        cc: 
        Subject:        Re: which Java version?


Hi Carl, I feel like we need to nail this down firmer than that. If 
we want to support clients at 1.4, for example, then that's a stake 
in the ground that has to be enforced by all qpid developers as it 
has a variety of implications on the implementation. We'd have to 
make sure that any parts of the code required for clients always 
remained at 1.4 and used only 1.4-compatible versions of underlying 
libraries, which implies that the qpid common code all has to be 1.4 
as well.

Personally, I think we should just say 1.5 across the board.

--steve

On Sep 8, 2006, at 6:27 PM, Carl Trieloff wrote:

>
> Java 1.5 or 1.6 for broker.
>
> For clients 1.4 might be good to also support.
>
> Carl.
>
> Steve Vinoski wrote:
>> Does Qpid mandate Java 5? The reason I ask is that I had some code 
>> checking turned on in my maven work and saw a ton of warnings 
>> about unchecked calls to collections classes. If we mandate 1.5, 
>> should we turn on such checking so we can make the code cleaner?
>>
>> --steve
>




This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
 

Re: which Java version?

Posted by Steve Vinoski <vi...@iona.com>.
Hi Carl, I feel like we need to nail this down firmer than that. If  
we want to support clients at 1.4, for example, then that's a stake  
in the ground that has to be enforced by all qpid developers as it  
has a variety of implications on the implementation. We'd have to  
make sure that any parts of the code required for clients always  
remained at 1.4 and used only 1.4-compatible versions of underlying  
libraries, which implies that the qpid common code all has to be 1.4  
as well.

Personally, I think we should just say 1.5 across the board.

--steve

On Sep 8, 2006, at 6:27 PM, Carl Trieloff wrote:

>
> Java 1.5 or 1.6 for broker.
>
> For clients 1.4 might be good to also support.
>
> Carl.
>
> Steve Vinoski wrote:
>> Does Qpid mandate Java 5? The reason I ask is that I had some code  
>> checking turned on in my maven work and saw a ton of warnings  
>> about unchecked calls to collections classes. If we mandate 1.5,  
>> should we turn on such checking so we can make the code cleaner?
>>
>> --steve
>


Re: which Java version?

Posted by Carl Trieloff <cc...@redhat.com>.
Java 1.5 or 1.6 for broker.

For clients 1.4 might be good to also support.

Carl.

Steve Vinoski wrote:
> Does Qpid mandate Java 5? The reason I ask is that I had some code 
> checking turned on in my maven work and saw a ton of warnings about 
> unchecked calls to collections classes. If we mandate 1.5, should we 
> turn on such checking so we can make the code cleaner?
>
> --steve