You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (Jira)" <ji...@apache.org> on 2022/03/29 22:37:00 UTC
[jira] [Commented] (MSHADE-393) Upgrade project from Java 7 to 8
[ https://issues.apache.org/jira/browse/MSHADE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514352#comment-17514352 ]
Karl Heinz Marbaise commented on MSHADE-393:
--------------------------------------------
Done in [33273411d30377773bc866bba46ec5f2fc39e60b|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=33273411d30377773bc866bba46ec5f2fc39e60b]
> Upgrade project from Java 7 to 8
> --------------------------------
>
> Key: MSHADE-393
> URL: https://issues.apache.org/jira/browse/MSHADE-393
> Project: Maven Shade Plugin
> Issue Type: Task
> Affects Versions: 3.2.4
> Reporter: Alexander Kriegisch
> Assignee: Karl Heinz Marbaise
> Priority: Major
> Fix For: 3.4.0
>
>
> If there is no specific reason forcing us to stay on Java source and target level 7, I suggest upgrading to Java 8. When working on pull requests, it felt quite uncomfortable not being able to use streams, interface default methods, lambdas.
> Is there a huge user base using Java 7 and still relying on Maven Shade upgrades? I.e. they want the latest features and bugfixes, but are unable to migrate to Java 8. That would be quite a sense of entitlement on their part.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)