Quoting Niclas Hedhman <[email protected]>:
Well, when you are a framework, you tend to try and stick to "lowest
possible denominator" to ensure its usefulness in as many places as
possible.
Minor things, like you mention, doesn't seem to validate moving up to
1.6 just yet, IMVHO.
True that. However, for the sake of just arguing against ;) and
bringing other points of view, I have to add the following: By forcing
the users of framework to adapt to newer technology, the robustness
and security will overall improve (here I assume that security and
robustness of JDK and Java improved from 1.5 to 1.6). This type of
behaviour could be described as "eliminating dinosaurs" - why
encourage people to stick with old technologies?
Well, I guess when SQL indexing will move from sandbox to actual
extensions / libraries repo, I have to remember to remove all
@Override annotations which cause errors in 1.5. Btw, what does V in
IMVHO stand for? "Very"?
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
