Let me clarify myself a bit, as I just had a chat session with Keith and
Christopher...
The concern I have is that moving to Java1.7 (jdk or jre), the second
bullet from below, is that this may force a departure from the typical
lifecycle for Accumulo 1.5. If the collective "we" are happy with the
potential to support Accumulo 1.5 and backport Accumulo 1.6
fixes/features to 1.5 as necessary for a period longer than we normally
do this, that's fine.
As there is an unquantifiable risk that is inherit to Java 1.7 (as any
new software), this is a real possibility. I haven't decided one way or
the other, but I wanted to make sure that the proponents of Java1.7 are
aware of such an impact.
On 6/3/13 5:04 PM, Josh Elser wrote:
Can you clarify what you mean?
- I would be ok with making JDK 1.7 the "default" for Accumulo 1.6.0. I
think this mostly boils down to the JDK which we would be performing our
testing with.
- I don't want to alienate JDK/JRE 1.6 users from using Accumulo 1.6.0,
so I am not in favor of removing the ability to run Accumulo 1.6.0 on
JRE 1.6.
I think the latter is acceptable to me as long as we document/advertise
how one could build Java 1.6 Accumulo 1.6.0 artifacts, if we choose not
to publish them ourselves.
Also, some quick searching leads me to believe that 1.6 bytecode will
run on a 1.7 JVM, but not vice versa. Does anyone know if this is the
case? I apologize if I'm bringing up an already-discussed subject.
On 6/3/13 4:51 PM, Christopher wrote:
Given all the previous discussions about this, and assuming all points
and counterpoints have already been sufficiently enumerated, I'd like
to put it to a vote, explicitly:
Should we switch to JDK 1.7 for Accumulo 1.6.0, to take advantage of
newer features (ACCUMULO-905), or should we continue to require that
Accumulo 1.6.0 run on JRE 1.6?
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
