Re: Dropping support for Java1.5

2011-03-14 Thread Hadrian Zbarcea
A few things, the most important being the ability to use dependencies that only support 1.6 (e.g. jersey). Even in previous versions released with jdk 1.5 support, some component did not work with jdk 1.5. That complicated our testing and packaging as well, and required extra time and effort to

Re: Dropping support for Java1.5

2011-03-14 Thread Grant Rettke
On Mon, Mar 14, 2011 at 9:47 AM, Hadrian Zbarcea wrote: > The cost/benefit ratio seemed to high for us. What does Camel gain from using JDK 1.6?

Re: Dropping support for Java1.5

2011-03-14 Thread Hadrian Zbarcea
On Mar 12, 2011, at 5:12 PM, Grant Rettke wrote: > On Sat, Mar 12, 2011 at 12:30 PM, bfischer wrote: >> 3. Furthermore our customers are "conservative", they don't like migrations >> to new versions. Thats true especially for their operating departments >> because it brings more work, increases

Re: Dropping support for Java1.5

2011-03-12 Thread Grant Rettke
On Sat, Mar 12, 2011 at 12:30 PM, bfischer wrote: > 3. Furthermore our customers are "conservative", they don't like migrations > to new versions. Thats true especially for their operating departments > because it brings more work, increases risks ... Customers are very conservative.

Re: Dropping support for Java1.5

2011-03-12 Thread bfischer
Hi Tarun, even it is sound strange, it has simple reasons: 1. Sun/Oracle JDK/JVM 5 reached its end of life. But they are other vendors out there like IBM (not sure about the status) and SAP, maybe more. 2. Big vendors like the before mentioned are shipping JVM as part of their "solutions", usual

Re: Dropping support for Java1.5

2011-03-11 Thread Tarun Ramakrishna
Hi, Why would any commercial environment still use Java 5 for current development considering it has passed its end of service life (with all the associated legal ramifications) ? -Tarun

Re: Dropping support for Java1.5

2011-03-10 Thread Claus Ibsen
On Thu, Mar 10, 2011 at 9:19 PM, bfischer wrote: > Hi Hadrian, Claus and Willem, > > many thanks for your feedback - thinking about I found it's worth to > continue on the path we started already. > Means: > > 1. Compiling Camel by our own like proposed by Hadrian (but it doesn't seems > to be tha

Re: Dropping support for Java1.5

2011-03-10 Thread bfischer
Hi Hadrian, Claus and Willem, many thanks for your feedback - thinking about I found it's worth to continue on the path we started already. Means: 1. Compiling Camel by our own like proposed by Hadrian (but it doesn't seems to be that easy) 2. I'll propose to my management to buy external support

Re: Dropping support for Java1.5

2011-03-09 Thread Claus Ibsen
On Thu, Mar 10, 2011 at 12:44 AM, Hadrian Zbarcea wrote: > Hi Bernd, > > First of thanks for using camel and for taking the time to express your > thoughts. Much appreciated. > > Comments inline. > > Hadrian > > On Mar 10, 2011, at 12:02 AM, bfischer wrote: > >> Hi all, >> >> Unfortunately I'm on

Re: Dropping support for Java1.5

2011-03-09 Thread Willem Jiang
On 3/10/11 7:02 AM, bfischer wrote: Hi all, Unfortunately I'm only subscribed to this list - so I recognized the announcement on the start page right now. That's my fault - but I like to follow invitation for a comment at the end of the announcement. First of all and to say it short - Camel is

Re: Dropping support for Java1.5

2011-03-09 Thread Hadrian Zbarcea
Hi Bernd, First of thanks for using camel and for taking the time to express your thoughts. Much appreciated. Comments inline. Hadrian On Mar 10, 2011, at 12:02 AM, bfischer wrote: > Hi all, > > Unfortunately I'm only subscribed to this list - so I recognized the > announcement on the start

Dropping support for Java1.5

2011-03-09 Thread bfischer
Hi all, Unfortunately I'm only subscribed to this list - so I recognized the announcement on the start page right now. That's my fault - but I like to follow invitation for a comment at the end of the announcement. First of all and to say it short - Camel is great and sure, developers decide abou