OK. Who cares if their last release was Java 1.5? They will never release another version that supports it.
Ralph > On Jun 5, 2017, at 12:55 PM, sebb <seb...@gmail.com> wrote: > > On 5 June 2017 at 20:26, Amey Jadiye <ameyjad...@gmail.com > <mailto:ameyjad...@gmail.com>> wrote: >> +1 >> >> I have seen hundreds of applications which are in (maintenance+ little >> enhancement) mode are already moved to higher versions of java ( >1.5 ), >> even very legacy applications which are just in maintenance mode or marked >> for decommission are already running on 1.6 as all know that there will be >> no updates. there could be rarest of rare applications running on 1.5 and >> sure they dont want move else they could have moved long back to 1.6 and >> and rarely 1.5 will move to java8 or 9 ;) >> >> so yeah, why are we discussing support for Java 1.5 when not even the >> vendors who ship it support it ? just move our modules for >=1.6. > > This thread is *not* about support for 1.5. > > It's about supporting Java 9, and what to do about components whose > last release is 1.5 or earlier. > > That is very different. > >> Regards, >> Amey >> >> On Mon, Jun 5, 2017 at 10:24 PM, Ralph Goers <ralph.go...@dslextreme.com> >> wrote: >> >>> This whole discussion has me really confused. According to >>> https://en.wikipedia.org/wiki/Java_version_history < >>> https://en.wikipedia.org/wiki/Java_version_history> the free version of >>> Java 5 reached end-of-life in 2009 and Oracle's supported version reached >>> end-of-life in 2015. https://developer.ibm.com/javasdk/support/lifecycle/ >>> <https://developer.ibm.com/javasdk/support/lifecycle/> doesn’t even show >>> Java 5 any more but https://www.ibm.com/developerworks/community/ >>> forums/html/topic?id=77777777-0000-0000-0000-000014807464 < >>> https://www.ibm.com/developerworks/community/ >>> forums/html/topic?id=77777777-0000-0000-0000-000014807464> indicates that >>> it also was dropped in 2015. >>> >>> So why are we discussing support for Java 1.5 when not even the vendors >>> who ship it support it? >>> >>> Ralph >>> >>> >>>> On Jun 5, 2017, at 9:45 AM, Gary Gregory <garydgreg...@gmail.com> wrote: >>>> >>>> On Mon, Jun 5, 2017 at 9:17 AM, Jochen Wiedmann < >>> jochen.wiedm...@gmail.com <mailto:jochen.wiedm...@gmail.com>> >>>> wrote: >>>> >>>>> On Mon, Jun 5, 2017 at 5:20 PM, sebb <seb...@gmail.com> wrote: >>>>> >>>>>>> I'd like us to be able to push out a new release with minimal changes >>>>>>> at any given time. If we have, for example, 1.6 as the target, and the >>>>>>> previous >>>>>>> release had 1.5 as the target, then we'd loose that ability, IMO. >>>>>>> (Think security releases.We've had quite a few in the past.) >>>>>> >>>>>> Understood, but I'm not sure why you feel the lack of a 1.6 release >>>>>> would prevent a security release. >>>>>> Surely we could just apply the fixes to the previously released code >>>>>> and change to 1.6 at the same time? >>>>> >>>>> Because the result clearly be binary incompatible to its predecessor, >>>>> and that's the whole point of such an emergency release. We'd want a >>>>> drop-in replacement. >>>>> >>>> >>>> If someone wants a fix for something that runs on 1.5, they are welcome >>> to >>>> provide a PR. I do not think we need to handcuff ourselves to Java 5. If >>>> your runtime is stuck on Java 5, your likely to have other more pressing >>>> security issues to address... >>>> >>>> Gary >>>> >>>>> >>>>> Jochen >>>>> >>>>> >>>>> -- >>>>> The next time you hear: "Don't reinvent the wheel!" >>>>> >>>>> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/ < >>> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/> >>>>> evolution-of-the-wheel-300x85.jpg >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org <mailto: >>> dev-unsubscr...@commons.apache.org> >>>>> For additional commands, e-mail: dev-h...@commons.apache.org <mailto: >>> dev-h...@commons.apache.org> >>> >> >> >> >> -- >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >> For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > <mailto:dev-unsubscr...@commons.apache.org> > For additional commands, e-mail: dev-h...@commons.apache.org > <mailto:dev-h...@commons.apache.org>
