[ImageJ-devel] [fiji-devel] moving to Java 7

[Curtis Rueden]

Hi all,

Mark Hiner wrote:
> my only hesitation towards agreeing with consensus here is that these
> particular mailing lists seem likely to be biased towards active
> developers (who I would expect to prefer newer Java versions).

I agree. While personally I would love to move to Java 7 or even Java 8,
and even if we all support that here, we must then ask on the main ImageJ
mailing list to get feedback from all users first.

Regards,
Curtis

On Fri, Dec 5, 2014 at 9:58 AM, Mark Hiner <hiner at wisc.edu> wrote:

> Jay,
> >Can anyone else confirm this experience?
> Yep, Yosemite dropped Java 6. Definitely an annoying extra barrier for
> developers. But there's a FAQ entry
> <http://imagej.net/Frequently_Asked_Questions#How_do_I_set_up_Java_6_on_OS_X.3F>
> now!
>
> Michael,
> >When replying to a post like this, is it the done thing to reply to the
> list in general or should I be replying just to the original poster?
> You did the right thing - reply to the whole list. That way there is a
> complete record of any discussion-especially important on a general topic
> like this. Personally, if I ever get a private mail in response to
> something, I cc the list in my reply (see also:
> http://imagej.net/Philosophy#Open_source)
>
> Out of curiosity, how do people feel about establishing set guidelines for
> when to advance Java versions (e.g. if it's 18 months past the end-of-life
> release and under 2% of the users would be affected, just upgrade)? There
> will certainly be times when this question will come up again... and my
> only hesitation towards agreeing with consensus here is that these
> particular mailing lists seem likely to be biased towards active developers
> (who I would expect to prefer newer Java versions).
>
> Best,
> Mark
>
> P.S. Thanks for starting this thread Tobias!
>
> On Fri, Dec 5, 2014 at 8:56 AM, Lee Kamentsky <leek at broadinstitute.org>
> wrote:
>
>> For CelllProfiler, there's some packaging work that would need to be done
>> (we bundle the JRE with the Windows version and the Centos 6 RPM has Java 6
>> as a dependency). We rely on the system Java for the Mac presently and I
>> don't have a clear idea of what range of Java 7 support to expect on our
>> user's Macs.
>>
>> It certainly seems like there is a lot of pressure to move to Java 7, so
>> my vote would be to move to Java 7, even considering the above.
>>
>> On Fri, Dec 5, 2014 at 8:54 AM, Tobias Pietzsch <pietzsch at mpi-cbg.de>
>> wrote:
>>
>>> Hi all,
>>>
>>> what is everyones opinion on moving the IJ2/Fiji stack to a new version
>>> of Java, i.e., Java 7.
>>> Java 7 has been around for more than 3 years now. The end-of-life final
>>> public release of Java 6 was more than 1.5 years ago.
>>>
>>> Benefits I see are the following:
>>>
>>> * We could use the “new" Java 7 libraries. For example the Fork/Join
>>> framework would come handy in defining multi-threading interfaces in
>>> scijava-common (to be used in imagej-ops for example). Or the NIO2 stuff
>>> (java.nio.file)
>>>
>>> * We would benefit from improvements of type inference for generics in
>>> the compiler. No more jumping through hoops to fix “errors” in code that
>>> should compile with Java 6 but doesn’t. (Plus we could use the diamond
>>> operator to shorten generics instantiations.)
>>>
>>> * We could use third-party libraries that only support Java 7. For
>>> example I’m using Jetty in a project that can therefore not be part of Fiji
>>> currently. (This mail was more or less triggered by me looking into
>>> http://ojalgo.org who maybe went a bit over the top and already
>>> abandoned Java 7 for Java 8). I think it is only a matter of time until we
>>> will have a problem with third-party libraries that we already use
>>> abandoning Java 6.
>>>
>>>
>>> I do not have a clear picture of what the downsides would be. Johannes
>>> always said that people on old macs are tied to an old java version and
>>> that we do not want to leave those users behind. It would be interesting to
>>> know how many people that actually would impact.
>>>
>>>
>>> What do you think?
>>>
>>> best regards,
>>> Tobias
>>>
>>>
>>> --
>>> --
>>> Please avoid top-posting, and please make sure to reply-to-all!
>>>
>>> Mailing list web interface: http://groups.google.com/group/fiji-devel
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Fiji-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to fiji-devel+unsubscribe at googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> --
>> Please avoid top-posting, and please make sure to reply-to-all!
>>
>> Mailing list web interface: http://groups.google.com/group/fiji-devel
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Fiji-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to fiji-devel+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> --
> Please avoid top-posting, and please make sure to reply-to-all!
>
> Mailing list web interface: http://groups.google.com/group/fiji-devel
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Fiji-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to fiji-devel+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20141205/cbfbfebb/attachment-0001.html>