On Mon, Jun 5, 2017 at 2:56 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
> > > On Jun 5, 2017, at 1:35 PM, sebb <seb...@gmail.com> wrote: > > > > On 5 June 2017 at 21:06, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > >> OK. Who cares if their last release was Java 1.5? They will never > release another version that supports it. > > > > Not sure who you mean by 'they' here. > > They is any component whose latest release is on Java 1.5. > > > > > This thread is about Commons components whose latest release is 1.5 or > > earlier, and what to do about it now that Java 9+ no longer supports > > 1.5 as a compiler option. > > The answer is clear. There is no problem using a component compiled for > Java 5, so this discussion is only about performing new releases of things. > Any component that has a latest release based on Java 5 will continue to > lay dormant until someone wants to do a new release of it. If and when that > happens the next release will use Java 6 or hopefully, Java 7 (since Java 6 > has already reached end-of-life as well but has about another year before > full end of support). There is no point in doing security fixes for > anything based on Java 5 (or 6 in my opinion). > > This discussion about Java 9 is just a red herring as it is forcing you to > have a discussion you really shouldn’t need to have. This upgrade should > have been forced eons ago. > +1 Gary > > Ralph > >
