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 test on both platforms. Not quite trivial and the benefit didn't seem significant enough to justify it.
Hadrian On Mar 14, 2011, at 11:08 AM, Grant Rettke wrote: > On Mon, Mar 14, 2011 at 9:47 AM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: >> The cost/benefit ratio seemed to high for us. > > What does Camel gain from using JDK 1.6?
