You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Dave <sn...@gmail.com> on 2019/05/12 18:25:52 UTC

Moving Roller master to Java 11

We've got a Pull Request that adds support for Java 11 in Roller.
   https://github.com/apache/roller/pull/14

Is anybody opposed to merging this PR and moving Roller's master branch to
Java 11?

I think the next major release of Roller (6.0) should include the new
Bootstrap based UI and should run on Java 11. Java 8 has been EOLed and
Java 11 is the current LTS version, so IMO it makes sense to upgrade.

I plan to continue to maintain Roller 5.x on Java 8 for the foreseeable
future.

Dave

Re: Moving Roller master to Java 11

Posted by Matt Raible <ma...@raibledesigns.com>.
+1

> On May 12, 2019, at 12:25, Dave <sn...@gmail.com> wrote:
> 
> We've got a Pull Request that adds support for Java 11 in Roller.
>   https://github.com/apache/roller/pull/14
> 
> Is anybody opposed to merging this PR and moving Roller's master branch to
> Java 11?
> 
> I think the next major release of Roller (6.0) should include the new
> Bootstrap based UI and should run on Java 11. Java 8 has been EOLed and
> Java 11 is the current LTS version, so IMO it makes sense to upgrade.
> 
> I plan to continue to maintain Roller 5.x on Java 8 for the foreseeable
> future.
> 
> Dave

Re: Moving Roller master to Java 11

Posted by Greg Huber <gr...@gmail.com>.
+1
...java8 is LTS till 2023! is struts java11?  I get some warnings on
startup last time I looked.

On Sun, 12 May 2019 at 19:26, Dave <sn...@gmail.com> wrote:

> We've got a Pull Request that adds support for Java 11 in Roller.
>    https://github.com/apache/roller/pull/14
>
> Is anybody opposed to merging this PR and moving Roller's master branch to
> Java 11?
>
> I think the next major release of Roller (6.0) should include the new
> Bootstrap based UI and should run on Java 11. Java 8 has been EOLed and
> Java 11 is the current LTS version, so IMO it makes sense to upgrade.
>
> I plan to continue to maintain Roller 5.x on Java 8 for the foreseeable
> future.
>
> Dave
>

Re: Moving Roller master to Java 11

Posted by sebb <se...@gmail.com>.
On Fri, 14 Jun 2019 at 19:17, Anil Gangolli <an...@busybuddha.org> wrote:
>
>
> You could poll.  Here are my votes:
>
> +1 on Java 11.  OpenJDK.  Free long-term support (LTS).  Language features.
>
> -1 on Java 7.  It has no security updates unless people are paying, and
> I expect most of the Roller installed base is not.

As I already noted, that is not relevant to the minimum Java version.

> Having to continue
> to support Java 7 is actually a disincentive for developers working on
> Roller because of the lack of modern features like lambdas and
> functional interfaces, for each, default methods, much better
> Collections, Atomics, and multi-threaded support.

At last!
This is the first time anyone has mentioned a valid reason for bumping
the minimum version of Java.
However, AFAICT most of those features are available in Java 8.

So what is it about Java 11 that is so compelling?


>
> On 6/14/19 5:19 AM, sebb wrote:
> > On Thu, 13 Jun 2019 at 15:39, Matt Raible <ma...@raibledesigns.com> wrote:
> >> There’s more bug fixes and security improvements in Java 11.
> > That is not an argument for increasing the minimum supported Java level.
> >
> > Those users that can upgrade to Java 11 easily can do so and take
> > advantage of the fixes.
> > Others can get security fixes for releases that are still supported.
> > This may involve payment, but at least the option is available.
> >
> >>> On Jun 13, 2019, at 06:22, sebb <se...@gmail.com> wrote:
> >>>
> >>>> On Wed, 12 Jun 2019 at 23:47, Dave <sn...@gmail.com> wrote:
> >>>>
> >>>>> On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:
> >>>>>
> >>>>>> On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
> >>>>>>
> >>>>>>> On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Note that Java 7 has extended support until July 2022.
> >>>>>>>
> >>>>>>> https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> >>>>>>>
> >>>>>>> Is there any pressing need to move to Java 11?
> >>>>>>>
> >>>>>> I'm not sure there is a pressing need, depending on how you define
> >>>>> pressing
> >>>>>> need, but the work is already done/ready to merge and multiple folks have
> >>>>>> expressed support for the upgrade. I think it makes sense to modernize
> >>>>>> Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.
> >>>>> Java 11 may well be better (one would hope so!)
> >>>>>
> >>>>> However, raising the minimum Java version means that existing users
> >>>>> may have to update their version of Java.
> >>>>> That is a generally a major undertaking for enterprises who need to
> >>>>> ensure that the new Java version is fully tested in their environment.
> >>>>
> >>>>
> >>>> That is true, but I think the number of enterprises using Roller is
> >>>> probably pretty small now. I think we have more to gain, as a project, by
> >>>> modernizing.
> >>> What are the benefits?
> >>> And does it make sense to go straight from Java 7 to Java 11?
> >>>
> >>> I'm not saying that the project should not upgrade.
> >>> However I believe it's important that the advantages and disadvantages
> >>> should be weighed up.
> >>>
> >>>> Plus, we've still got Roller 5 for those folks.  Also, I've
> >>>> talked to ASF INFRA about Roller 6 and they are fine with upgrading for
> >>>> Roller 6.
> >>>>
> >>>> Dave
>
>

Re: Moving Roller master to Java 11

Posted by Dave <sn...@gmail.com>.
Thanks Matt, Greg, Sebb and Anil for considering this question and
providing good feedback.

I think the consensus is that the PR should be merged, thus moving master
to Java 11 and the new Bootstrap UI.

Dave


On Fri, Jun 14, 2019 at 2:17 PM Anil Gangolli <an...@busybuddha.org> wrote:

>
> You could poll.  Here are my votes:
>
> +1 on Java 11.  OpenJDK.  Free long-term support (LTS).  Language features.
>
> -1 on Java 7.  It has no security updates unless people are paying, and
> I expect most of the Roller installed base is not.  Having to continue
> to support Java 7 is actually a disincentive for developers working on
> Roller because of the lack of modern features like lambdas and
> functional interfaces, for each, default methods, much better
> Collections, Atomics, and multi-threaded support.
>
>
> On 6/14/19 5:19 AM, sebb wrote:
> > On Thu, 13 Jun 2019 at 15:39, Matt Raible <ma...@raibledesigns.com>
> wrote:
> >> There’s more bug fixes and security improvements in Java 11.
> > That is not an argument for increasing the minimum supported Java level.
> >
> > Those users that can upgrade to Java 11 easily can do so and take
> > advantage of the fixes.
> > Others can get security fixes for releases that are still supported.
> > This may involve payment, but at least the option is available.
> >
> >>> On Jun 13, 2019, at 06:22, sebb <se...@gmail.com> wrote:
> >>>
> >>>> On Wed, 12 Jun 2019 at 23:47, Dave <sn...@gmail.com> wrote:
> >>>>
> >>>>> On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:
> >>>>>
> >>>>>> On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
> >>>>>>
> >>>>>>> On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Note that Java 7 has extended support until July 2022.
> >>>>>>>
> >>>>>>>
> https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> >>>>>>>
> >>>>>>> Is there any pressing need to move to Java 11?
> >>>>>>>
> >>>>>> I'm not sure there is a pressing need, depending on how you define
> >>>>> pressing
> >>>>>> need, but the work is already done/ready to merge and multiple
> folks have
> >>>>>> expressed support for the upgrade. I think it makes sense to
> modernize
> >>>>>> Roller and dependencies and Java 11 is generally better than 1.7
> and 1.8.
> >>>>> Java 11 may well be better (one would hope so!)
> >>>>>
> >>>>> However, raising the minimum Java version means that existing users
> >>>>> may have to update their version of Java.
> >>>>> That is a generally a major undertaking for enterprises who need to
> >>>>> ensure that the new Java version is fully tested in their
> environment.
> >>>>
> >>>>
> >>>> That is true, but I think the number of enterprises using Roller is
> >>>> probably pretty small now. I think we have more to gain, as a
> project, by
> >>>> modernizing.
> >>> What are the benefits?
> >>> And does it make sense to go straight from Java 7 to Java 11?
> >>>
> >>> I'm not saying that the project should not upgrade.
> >>> However I believe it's important that the advantages and disadvantages
> >>> should be weighed up.
> >>>
> >>>> Plus, we've still got Roller 5 for those folks.  Also, I've
> >>>> talked to ASF INFRA about Roller 6 and they are fine with upgrading
> for
> >>>> Roller 6.
> >>>>
> >>>> Dave
>
>
>

Re: Moving Roller master to Java 11

Posted by Anil Gangolli <an...@busybuddha.org>.
You could poll.  Here are my votes:

+1 on Java 11.  OpenJDK.  Free long-term support (LTS).  Language features.

-1 on Java 7.  It has no security updates unless people are paying, and 
I expect most of the Roller installed base is not.  Having to continue 
to support Java 7 is actually a disincentive for developers working on 
Roller because of the lack of modern features like lambdas and 
functional interfaces, for each, default methods, much better 
Collections, Atomics, and multi-threaded support.


On 6/14/19 5:19 AM, sebb wrote:
> On Thu, 13 Jun 2019 at 15:39, Matt Raible <ma...@raibledesigns.com> wrote:
>> There’s more bug fixes and security improvements in Java 11.
> That is not an argument for increasing the minimum supported Java level.
>
> Those users that can upgrade to Java 11 easily can do so and take
> advantage of the fixes.
> Others can get security fixes for releases that are still supported.
> This may involve payment, but at least the option is available.
>
>>> On Jun 13, 2019, at 06:22, sebb <se...@gmail.com> wrote:
>>>
>>>> On Wed, 12 Jun 2019 at 23:47, Dave <sn...@gmail.com> wrote:
>>>>
>>>>> On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:
>>>>>
>>>>>> On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
>>>>>>
>>>>>>> On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
>>>>>>>
>>>>>>> Note that Java 7 has extended support until July 2022.
>>>>>>>
>>>>>>> https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>>>>>>>
>>>>>>> Is there any pressing need to move to Java 11?
>>>>>>>
>>>>>> I'm not sure there is a pressing need, depending on how you define
>>>>> pressing
>>>>>> need, but the work is already done/ready to merge and multiple folks have
>>>>>> expressed support for the upgrade. I think it makes sense to modernize
>>>>>> Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.
>>>>> Java 11 may well be better (one would hope so!)
>>>>>
>>>>> However, raising the minimum Java version means that existing users
>>>>> may have to update their version of Java.
>>>>> That is a generally a major undertaking for enterprises who need to
>>>>> ensure that the new Java version is fully tested in their environment.
>>>>
>>>>
>>>> That is true, but I think the number of enterprises using Roller is
>>>> probably pretty small now. I think we have more to gain, as a project, by
>>>> modernizing.
>>> What are the benefits?
>>> And does it make sense to go straight from Java 7 to Java 11?
>>>
>>> I'm not saying that the project should not upgrade.
>>> However I believe it's important that the advantages and disadvantages
>>> should be weighed up.
>>>
>>>> Plus, we've still got Roller 5 for those folks.  Also, I've
>>>> talked to ASF INFRA about Roller 6 and they are fine with upgrading for
>>>> Roller 6.
>>>>
>>>> Dave



Re: Moving Roller master to Java 11

Posted by sebb <se...@gmail.com>.
On Thu, 13 Jun 2019 at 15:39, Matt Raible <ma...@raibledesigns.com> wrote:
>
> There’s more bug fixes and security improvements in Java 11.

That is not an argument for increasing the minimum supported Java level.

Those users that can upgrade to Java 11 easily can do so and take
advantage of the fixes.
Others can get security fixes for releases that are still supported.
This may involve payment, but at least the option is available.

> > On Jun 13, 2019, at 06:22, sebb <se...@gmail.com> wrote:
> >
> >> On Wed, 12 Jun 2019 at 23:47, Dave <sn...@gmail.com> wrote:
> >>
> >>> On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:
> >>>
> >>>> On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
> >>>>
> >>>>> On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
> >>>>>
> >>>>> Note that Java 7 has extended support until July 2022.
> >>>>>
> >>>>> https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> >>>>>
> >>>>> Is there any pressing need to move to Java 11?
> >>>>>
> >>>>
> >>>> I'm not sure there is a pressing need, depending on how you define
> >>> pressing
> >>>> need, but the work is already done/ready to merge and multiple folks have
> >>>> expressed support for the upgrade. I think it makes sense to modernize
> >>>> Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.
> >>>
> >>> Java 11 may well be better (one would hope so!)
> >>>
> >>> However, raising the minimum Java version means that existing users
> >>> may have to update their version of Java.
> >>> That is a generally a major undertaking for enterprises who need to
> >>> ensure that the new Java version is fully tested in their environment.
> >>
> >>
> >>
> >> That is true, but I think the number of enterprises using Roller is
> >> probably pretty small now. I think we have more to gain, as a project, by
> >> modernizing.
> >
> > What are the benefits?
> > And does it make sense to go straight from Java 7 to Java 11?
> >
> > I'm not saying that the project should not upgrade.
> > However I believe it's important that the advantages and disadvantages
> > should be weighed up.
> >
> >> Plus, we've still got Roller 5 for those folks.  Also, I've
> >> talked to ASF INFRA about Roller 6 and they are fine with upgrading for
> >> Roller 6.
> >>
> >> Dave

Re: Moving Roller master to Java 11

Posted by Matt Raible <ma...@raibledesigns.com>.
There’s more bug fixes and security improvements in Java 11.

> On Jun 13, 2019, at 06:22, sebb <se...@gmail.com> wrote:
> 
>> On Wed, 12 Jun 2019 at 23:47, Dave <sn...@gmail.com> wrote:
>> 
>>> On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:
>>> 
>>>> On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
>>>> 
>>>>> On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
>>>>> 
>>>>> Note that Java 7 has extended support until July 2022.
>>>>> 
>>>>> https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>>>>> 
>>>>> Is there any pressing need to move to Java 11?
>>>>> 
>>>> 
>>>> I'm not sure there is a pressing need, depending on how you define
>>> pressing
>>>> need, but the work is already done/ready to merge and multiple folks have
>>>> expressed support for the upgrade. I think it makes sense to modernize
>>>> Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.
>>> 
>>> Java 11 may well be better (one would hope so!)
>>> 
>>> However, raising the minimum Java version means that existing users
>>> may have to update their version of Java.
>>> That is a generally a major undertaking for enterprises who need to
>>> ensure that the new Java version is fully tested in their environment.
>> 
>> 
>> 
>> That is true, but I think the number of enterprises using Roller is
>> probably pretty small now. I think we have more to gain, as a project, by
>> modernizing.
> 
> What are the benefits?
> And does it make sense to go straight from Java 7 to Java 11?
> 
> I'm not saying that the project should not upgrade.
> However I believe it's important that the advantages and disadvantages
> should be weighed up.
> 
>> Plus, we've still got Roller 5 for those folks.  Also, I've
>> talked to ASF INFRA about Roller 6 and they are fine with upgrading for
>> Roller 6.
>> 
>> Dave

Re: Moving Roller master to Java 11

Posted by sebb <se...@gmail.com>.
On Wed, 12 Jun 2019 at 23:47, Dave <sn...@gmail.com> wrote:
>
> On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:
>
> > On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
> > >
> > > On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
> > >
> > > > Note that Java 7 has extended support until July 2022.
> > > >
> > > > https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> > > >
> > > > Is there any pressing need to move to Java 11?
> > > >
> > >
> > > I'm not sure there is a pressing need, depending on how you define
> > pressing
> > > need, but the work is already done/ready to merge and multiple folks have
> > > expressed support for the upgrade. I think it makes sense to modernize
> > > Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.
> >
> > Java 11 may well be better (one would hope so!)
> >
> > However, raising the minimum Java version means that existing users
> > may have to update their version of Java.
> > That is a generally a major undertaking for enterprises who need to
> > ensure that the new Java version is fully tested in their environment.
>
>
>
> That is true, but I think the number of enterprises using Roller is
> probably pretty small now. I think we have more to gain, as a project, by
> modernizing.

What are the benefits?
And does it make sense to go straight from Java 7 to Java 11?

I'm not saying that the project should not upgrade.
However I believe it's important that the advantages and disadvantages
should be weighed up.

> Plus, we've still got Roller 5 for those folks.  Also, I've
> talked to ASF INFRA about Roller 6 and they are fine with upgrading for
> Roller 6.
>
> Dave

Re: Moving Roller master to Java 11

Posted by Dave <sn...@gmail.com>.
On Wed, Jun 12, 2019 at 6:19 AM sebb <se...@gmail.com> wrote:

> On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
> >
> > On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
> >
> > > Note that Java 7 has extended support until July 2022.
> > >
> > > https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> > >
> > > Is there any pressing need to move to Java 11?
> > >
> >
> > I'm not sure there is a pressing need, depending on how you define
> pressing
> > need, but the work is already done/ready to merge and multiple folks have
> > expressed support for the upgrade. I think it makes sense to modernize
> > Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.
>
> Java 11 may well be better (one would hope so!)
>
> However, raising the minimum Java version means that existing users
> may have to update their version of Java.
> That is a generally a major undertaking for enterprises who need to
> ensure that the new Java version is fully tested in their environment.



That is true, but I think the number of enterprises using Roller is
probably pretty small now. I think we have more to gain, as a project, by
modernizing. Plus, we've still got Roller 5 for those folks.  Also, I've
talked to ASF INFRA about Roller 6 and they are fine with upgrading for
Roller 6.

Dave

Re: Moving Roller master to Java 11

Posted by sebb <se...@gmail.com>.
On Wed, 12 Jun 2019 at 02:23, Dave <sn...@gmail.com> wrote:
>
> On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:
>
> > Note that Java 7 has extended support until July 2022.
> >
> > https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> >
> > Is there any pressing need to move to Java 11?
> >
>
> I'm not sure there is a pressing need, depending on how you define pressing
> need, but the work is already done/ready to merge and multiple folks have
> expressed support for the upgrade. I think it makes sense to modernize
> Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.

Java 11 may well be better (one would hope so!)

However, raising the minimum Java version means that existing users
may have to update their version of Java.
That is a generally a major undertaking for enterprises who need to
ensure that the new Java version is fully tested in their environment.


> Dave
>
>
>
>
>
>
> > On Sun, 9 Jun 2019 at 22:10, Dave <sn...@gmail.com> wrote:
> > >
> > > I've been running Roller 6.0.0-SNAPSHOT under Java 11 on my site for a
> > > while now. Unless somebody objects, I plan to merge boostrap-ui which
> > > contains the new Boostrap UI for Roller and moves Roller to Java 11 this
> > > week.
> > >
> > > Thanks,
> > > Dave
> > >
> > >
> > > On Tue, May 14, 2019 at 4:59 AM Greg Huber <gr...@gmail.com> wrote:
> > >
> > > > for java11 email was troublesome as jaf was removed, also now its
> > morphed :
> > > > https://eclipse-ee4j.github.io/javamail/
> > > > <dependency>
> > > >     <groupId>com.sun.mail</groupId>
> > > >     <artifactId>jakarta.mail</artifactId>
> > > >     <version>1.6.3</version>
> > > >     <scope>provided</scope>
> > > > </dependency>
> > > >
> > > > Cheers Greg
> > > >
> > > > On Sun, 12 May 2019 at 19:26, Dave <sn...@gmail.com> wrote:
> > > >
> > > > > We've got a Pull Request that adds support for Java 11 in Roller.
> > > > >    https://github.com/apache/roller/pull/14
> > > > >
> > > > > Is anybody opposed to merging this PR and moving Roller's master
> > branch
> > > > to
> > > > > Java 11?
> > > > >
> > > > > I think the next major release of Roller (6.0) should include the new
> > > > > Bootstrap based UI and should run on Java 11. Java 8 has been EOLed
> > and
> > > > > Java 11 is the current LTS version, so IMO it makes sense to upgrade.
> > > > >
> > > > > I plan to continue to maintain Roller 5.x on Java 8 for the
> > foreseeable
> > > > > future.
> > > > >
> > > > > Dave
> > > > >
> > > >
> >

Re: Moving Roller master to Java 11

Posted by Dave <sn...@gmail.com>.
On Mon, Jun 10, 2019 at 6:03 AM sebb <se...@gmail.com> wrote:

> Note that Java 7 has extended support until July 2022.
>
> https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>
> Is there any pressing need to move to Java 11?
>

I'm not sure there is a pressing need, depending on how you define pressing
need, but the work is already done/ready to merge and multiple folks have
expressed support for the upgrade. I think it makes sense to modernize
Roller and dependencies and Java 11 is generally better than 1.7 and 1.8.

Dave






> On Sun, 9 Jun 2019 at 22:10, Dave <sn...@gmail.com> wrote:
> >
> > I've been running Roller 6.0.0-SNAPSHOT under Java 11 on my site for a
> > while now. Unless somebody objects, I plan to merge boostrap-ui which
> > contains the new Boostrap UI for Roller and moves Roller to Java 11 this
> > week.
> >
> > Thanks,
> > Dave
> >
> >
> > On Tue, May 14, 2019 at 4:59 AM Greg Huber <gr...@gmail.com> wrote:
> >
> > > for java11 email was troublesome as jaf was removed, also now its
> morphed :
> > > https://eclipse-ee4j.github.io/javamail/
> > > <dependency>
> > >     <groupId>com.sun.mail</groupId>
> > >     <artifactId>jakarta.mail</artifactId>
> > >     <version>1.6.3</version>
> > >     <scope>provided</scope>
> > > </dependency>
> > >
> > > Cheers Greg
> > >
> > > On Sun, 12 May 2019 at 19:26, Dave <sn...@gmail.com> wrote:
> > >
> > > > We've got a Pull Request that adds support for Java 11 in Roller.
> > > >    https://github.com/apache/roller/pull/14
> > > >
> > > > Is anybody opposed to merging this PR and moving Roller's master
> branch
> > > to
> > > > Java 11?
> > > >
> > > > I think the next major release of Roller (6.0) should include the new
> > > > Bootstrap based UI and should run on Java 11. Java 8 has been EOLed
> and
> > > > Java 11 is the current LTS version, so IMO it makes sense to upgrade.
> > > >
> > > > I plan to continue to maintain Roller 5.x on Java 8 for the
> foreseeable
> > > > future.
> > > >
> > > > Dave
> > > >
> > >
>

Re: Moving Roller master to Java 11

Posted by sebb <se...@gmail.com>.
Note that Java 7 has extended support until July 2022.

https://www.oracle.com/technetwork/java/java-se-support-roadmap.html

Is there any pressing need to move to Java 11?

S.
On Sun, 9 Jun 2019 at 22:10, Dave <sn...@gmail.com> wrote:
>
> I've been running Roller 6.0.0-SNAPSHOT under Java 11 on my site for a
> while now. Unless somebody objects, I plan to merge boostrap-ui which
> contains the new Boostrap UI for Roller and moves Roller to Java 11 this
> week.
>
> Thanks,
> Dave
>
>
> On Tue, May 14, 2019 at 4:59 AM Greg Huber <gr...@gmail.com> wrote:
>
> > for java11 email was troublesome as jaf was removed, also now its morphed :
> > https://eclipse-ee4j.github.io/javamail/
> > <dependency>
> >     <groupId>com.sun.mail</groupId>
> >     <artifactId>jakarta.mail</artifactId>
> >     <version>1.6.3</version>
> >     <scope>provided</scope>
> > </dependency>
> >
> > Cheers Greg
> >
> > On Sun, 12 May 2019 at 19:26, Dave <sn...@gmail.com> wrote:
> >
> > > We've got a Pull Request that adds support for Java 11 in Roller.
> > >    https://github.com/apache/roller/pull/14
> > >
> > > Is anybody opposed to merging this PR and moving Roller's master branch
> > to
> > > Java 11?
> > >
> > > I think the next major release of Roller (6.0) should include the new
> > > Bootstrap based UI and should run on Java 11. Java 8 has been EOLed and
> > > Java 11 is the current LTS version, so IMO it makes sense to upgrade.
> > >
> > > I plan to continue to maintain Roller 5.x on Java 8 for the foreseeable
> > > future.
> > >
> > > Dave
> > >
> >

Re: Moving Roller master to Java 11

Posted by Dave <sn...@gmail.com>.
I've been running Roller 6.0.0-SNAPSHOT under Java 11 on my site for a
while now. Unless somebody objects, I plan to merge boostrap-ui which
contains the new Boostrap UI for Roller and moves Roller to Java 11 this
week.

Thanks,
Dave


On Tue, May 14, 2019 at 4:59 AM Greg Huber <gr...@gmail.com> wrote:

> for java11 email was troublesome as jaf was removed, also now its morphed :
> https://eclipse-ee4j.github.io/javamail/
> <dependency>
>     <groupId>com.sun.mail</groupId>
>     <artifactId>jakarta.mail</artifactId>
>     <version>1.6.3</version>
>     <scope>provided</scope>
> </dependency>
>
> Cheers Greg
>
> On Sun, 12 May 2019 at 19:26, Dave <sn...@gmail.com> wrote:
>
> > We've got a Pull Request that adds support for Java 11 in Roller.
> >    https://github.com/apache/roller/pull/14
> >
> > Is anybody opposed to merging this PR and moving Roller's master branch
> to
> > Java 11?
> >
> > I think the next major release of Roller (6.0) should include the new
> > Bootstrap based UI and should run on Java 11. Java 8 has been EOLed and
> > Java 11 is the current LTS version, so IMO it makes sense to upgrade.
> >
> > I plan to continue to maintain Roller 5.x on Java 8 for the foreseeable
> > future.
> >
> > Dave
> >
>

Re: Moving Roller master to Java 11

Posted by Greg Huber <gr...@gmail.com>.
for java11 email was troublesome as jaf was removed, also now its morphed :
https://eclipse-ee4j.github.io/javamail/
<dependency>
    <groupId>com.sun.mail</groupId>
    <artifactId>jakarta.mail</artifactId>
    <version>1.6.3</version>
    <scope>provided</scope>
</dependency>

Cheers Greg

On Sun, 12 May 2019 at 19:26, Dave <sn...@gmail.com> wrote:

> We've got a Pull Request that adds support for Java 11 in Roller.
>    https://github.com/apache/roller/pull/14
>
> Is anybody opposed to merging this PR and moving Roller's master branch to
> Java 11?
>
> I think the next major release of Roller (6.0) should include the new
> Bootstrap based UI and should run on Java 11. Java 8 has been EOLed and
> Java 11 is the current LTS version, so IMO it makes sense to upgrade.
>
> I plan to continue to maintain Roller 5.x on Java 8 for the foreseeable
> future.
>
> Dave
>