[jira] [Commented] (NIFI-10147) Remove Support for Java 8
[ https://issues.apache.org/jira/browse/NIFI-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565137#comment-17565137 ] David Handermann commented on NIFI-10147: - Thanks for the comment [~Chris S]. It seems like we should consider upgrading Docker builds to Java 11 earlier. That will provide some opportunity for additional exercise of Java 11 prior to removing support for Java 8. > Remove Support for Java 8 > - > > Key: NIFI-10147 > URL: https://issues.apache.org/jira/browse/NIFI-10147 > Project: Apache NiFi > Issue Type: Epic > Components: Core Framework, MiNiFi, NiFi Registry, NiFi Stateless >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Although multiple vendors have planned extended support for Java 8, a number > of projects are in the process of deprecating and removing support for Java > 8. These projects include the following: > - [Jetty 9.4|https://github.com/eclipse/jetty.project/issues/7958] > - [Spring > 5|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6] > - [OpenSAML 3|https://shibboleth.atlassian.net/wiki/spaces/OSAML/overview] > Apache NiFi should also remove support for Java 8 in order to maintain active > support for various components. > Removing support for Java 8 requires a new major version release and will > also require several build configuration changes including the following: > - Updating Maven source and compiler settings > - Updating minimum Java build version > - Removing optional Maven build profiles > - Updating GitHub workflows > Initial discussion on a migration strategy included a tentative target of the > end of calendar year 2022. > Implementation should not proceed until after a minor release of Apache NiFi > 1.17.0. > Mailing list discussion: > [https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10147) Remove Support for Java 8
[ https://issues.apache.org/jira/browse/NIFI-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562231#comment-17562231 ] Chris Sampson commented on NIFI-10147: -- Docker builds will need to be updated to (at least) Java 11. Are the changes being made across all NiFi artifacts, e.g. NiFi Registry and MiNiFi (Java) too - worth clarifying that probably. > Remove Support for Java 8 > - > > Key: NIFI-10147 > URL: https://issues.apache.org/jira/browse/NIFI-10147 > Project: Apache NiFi > Issue Type: Epic > Components: Core Framework, MiNiFi, NiFi Registry, NiFi Stateless >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Although multiple vendors have planned extended support for Java 8, a number > of projects are in the process of deprecating and removing support for Java > 8. These projects include the following: > - [Jetty 9.4|https://github.com/eclipse/jetty.project/issues/7958] > - [Spring > 5|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6] > - [OpenSAML 3|https://shibboleth.atlassian.net/wiki/spaces/OSAML/overview] > Apache NiFi should also remove support for Java 8 in order to maintain active > support for various components. > Removing support for Java 8 requires a new major version release and will > also require several build configuration changes including the following: > - Updating Maven source and compiler settings > - Updating minimum Java build version > - Removing optional Maven build profiles > - Updating GitHub workflows > Initial discussion on a migration strategy included a tentative target of the > end of calendar year 2022. > Implementation should not proceed until after a minor release of Apache NiFi > 1.17.0. > Mailing list discussion: > [https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10147) Remove Support for Java 8
[ https://issues.apache.org/jira/browse/NIFI-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557127#comment-17557127 ] Pierre Villard commented on NIFI-10147: --- Something I would consider for removal with NiFi 2.0 is the concept of variables. > Remove Support for Java 8 > - > > Key: NIFI-10147 > URL: https://issues.apache.org/jira/browse/NIFI-10147 > Project: Apache NiFi > Issue Type: Epic > Components: Core Framework, MiNiFi, NiFi Registry, NiFi Stateless >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Although multiple vendors have planned extended support for Java 8, a number > of projects are in the process of deprecating and removing support for Java > 8. These projects include the following: > - [Jetty 9.4|https://github.com/eclipse/jetty.project/issues/7958] > - [Spring > 5|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6] > - [OpenSAML 3|https://shibboleth.atlassian.net/wiki/spaces/OSAML/overview] > Apache NiFi should also remove support for Java 8 in order to maintain active > support for various components. > Removing support for Java 8 requires a new major version release and will > also require several build configuration changes including the following: > - Updating Maven source and compiler settings > - Updating minimum Java build version > - Removing optional Maven build profiles > - Updating GitHub workflows > Initial discussion on a migration strategy included a tentative target of the > end of calendar year 2022. > Implementation should not proceed until after a minor release of Apache NiFi > 1.17.0. > Mailing list discussion: > [https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10147) Remove Support for Java 8
[ https://issues.apache.org/jira/browse/NIFI-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557042#comment-17557042 ] David Handermann commented on NIFI-10147: - That's a good question [~kdoran]. Too many changes could become difficult to rebase, however, the initial scope of changes should be minimal. Given that automated builds already include Java 11 and Java 17, initial removal of Java 8 should require minimal changes. Removing optional Maven build profiles could be a bit more involved, and there may be some incremental work that could be accomplished on the current main branch prior to removing Java 8 support. For now, it seems better to wait on creating a separate branch, but open to additional reasons why it might be helpful sooner rather than later. > Remove Support for Java 8 > - > > Key: NIFI-10147 > URL: https://issues.apache.org/jira/browse/NIFI-10147 > Project: Apache NiFi > Issue Type: Epic > Components: Core Framework, MiNiFi, NiFi Registry, NiFi Stateless >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Although multiple vendors have planned extended support for Java 8, a number > of projects are in the process of deprecating and removing support for Java > 8. These projects include the following: > - [Jetty 9.4|https://github.com/eclipse/jetty.project/issues/7958] > - [Spring > 5|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6] > - [OpenSAML 3|https://shibboleth.atlassian.net/wiki/spaces/OSAML/overview] > Apache NiFi should also remove support for Java 8 in order to maintain active > support for various components. > Removing support for Java 8 requires a new major version release and will > also require several build configuration changes including the following: > - Updating Maven source and compiler settings > - Updating minimum Java build version > - Removing optional Maven build profiles > - Updating GitHub workflows > Initial discussion on a migration strategy included a tentative target of the > end of calendar year 2022. > Implementation should not proceed until after a minor release of Apache NiFi > 1.17.0. > Mailing list discussion: > [https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10147) Remove Support for Java 8
[ https://issues.apache.org/jira/browse/NIFI-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557038#comment-17557038 ] Kevin Doran commented on NIFI-10147: Do we want to make a 2.0 development branch in the central code repository? I'm thinking it would be a place that experimental work could begin, to be continually rebased on main, until we are ready to release 2.0, at which point we could push the 2.0 development branch to main. Would this be helpful to start making progress? Would rebases be too complicated to sustain this work? > Remove Support for Java 8 > - > > Key: NIFI-10147 > URL: https://issues.apache.org/jira/browse/NIFI-10147 > Project: Apache NiFi > Issue Type: Epic > Components: Core Framework, MiNiFi, NiFi Registry, NiFi Stateless >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Although multiple vendors have planned extended support for Java 8, a number > of projects are in the process of deprecating and removing support for Java > 8. These projects include the following: > - [Jetty 9.4|https://github.com/eclipse/jetty.project/issues/7958] > - [Spring > 5|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6] > - [OpenSAML 3|https://shibboleth.atlassian.net/wiki/spaces/OSAML/overview] > Apache NiFi should also remove support for Java 8 in order to maintain active > support for various components. > Removing support for Java 8 requires a new major version release and will > also require several build configuration changes including the following: > - Updating Maven source and compiler settings > - Updating minimum Java build version > - Removing optional Maven build profiles > - Updating GitHub workflows > Initial discussion on a migration strategy included a tentative target of the > end of calendar year 2022. > Implementation should not proceed until after a minor release of Apache NiFi > 1.17.0. > Mailing list discussion: > [https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34] -- This message was sent by Atlassian Jira (v8.20.7#820007)
