On 26/10/2019 09:27, Garry Hurley wrote:
> -1
> 
> While I agree it is good to support Java 11, forcing a move to Java 11 will
> hamstring some users of James.  First of all, government agencies are slow
> to adopt new versions, mainly because they have few actual employees
> well-versed enough to know what enhancements the new versions of Java would
> do.  Additionally, they have other legacy applications which require older
> versions of Java to run, often on the same machine as their James server.

Running different applications with different versions of Java does not
seem an issue to me.

> That being said, I do think moving to Java 11 is a good strategy, but
> keeping compatibility with Java 8 is essential for now.  I would ensure
> that you compile to Java 8 standards in order to help wider adoption.

That could be a solution to me. We could let the time between to
releases for people to adapt.

> Please do not recompile older binaries into Java 11, as some of us have to
> jump through sixteen flaming hoops in gasoline-soaked coveralls in order to
> get approval to get a version of James installed, let alone get Java
> upgraded to a proper version.

That won't happen.

Also keep in mind that Apache delivers code, binaries are just here for
convenience. (old release code will be unchanged anyway, and you will be
able to recompile to JRE 8)

> Also, the packages of Java that have been
> bundled with and which have patches in different versions of Red Hat
> Enterprise Linux and SuSE Linux Enterprise Server are not just able to
> install the latest and greatest Linux.

Getting a JRE that is still maintained looks like a big deal to me, I
believe such governement agencies would feel the same. And maybe it's
not packaged out of the box but you should still be able to install a
JRE 11 on such old machines.

> On Thu, Oct 24, 2019 at 10:43 AM Matthieu Baechler <matth...@apache.org>
> wrote:
> 
>> Hi,
>>
>> I would like to propose the migration to Java 11 as a runtime.
>>
>> I opened an ADR here: https://github.com/apache/james-project/pull/174
>>
>> Here is the content of this ADR:
>>
>> -------------------------------------------------------------------
>> # 9. Migration to Java Runtime Environment 11
>>
>> Date: 2019-10-24
>>
>> ## Status
>>
>> Proposed
>>
>> ## Context
>>
>> Java 11 is the only "Long Term Support" java release right now so more
>> and more people will use it exclusively.
>>
>> James is known to build with Java Compiler 11 for some weeks.
>>
>> ## Decision
>>
>> We adopt Java Runtime Environment 11 for James as a runtime to benefits
>> from a supported runtime and new features
>> of the languages and the platform.
>>
>> ## Consequences
>>
>> * It requires the upgrade of Spring to 4.3.x.
>> * All docker images should be updated to adoptopenjdk 11.
>> * The documentation should be updated accordingly.
>>
>> -------------------------------------------------------------------
>>
>> Voting rules:
>>
>> I do propose a vote to ensure consensus on it:
>>  - Answer this mail with "+1" to support this decision
>>  - Answer this mail with "-1" if you reject this decision
>>
>> Negative votes should be motivated. Voting ends on 31th October 2019
>> 8am UTC.
>>
>> Cheers,
>>
>> --
>> Matthieu Baechler
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
>> For additional commands, e-mail: server-dev-h...@james.apache.org
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to