[
https://issues.apache.org/jira/browse/MSHADE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514421#comment-17514421
]
Hudson commented on MSHADE-393:
-------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-shade-plugin » master #12
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-shade-plugin/job/master/12/
> 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)
