[
https://issues.apache.org/jira/browse/MSHARED-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072681#comment-15072681
]
Michael Osipov commented on MSHARED-409:
----------------------------------------
Probably, yes -- but the Findbugs fork is the best we can use at the moment.
Though I am a Commons committer, I simply don't have the time to make the BCEL
6.0 release.
> maven-shared-jar fails to analyse JARs containing Java 8 code
> -------------------------------------------------------------
>
> Key: MSHARED-409
> URL: https://issues.apache.org/jira/browse/MSHARED-409
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-shared-jar
> Affects Versions: maven-shared-jar-1.1
> Environment: windows 8.1 jdk 8.31
> Reporter: Eric Barboni
> Assignee: Michael Osipov
> Fix For: maven-shared-jar-1.2
>
> Attachments: jdk8.patch, jdk8jar.zip
>
>
> Maven shared jar fail to analyse jdk8 artifact (containing jdk8 stream ).
> Apache BCEL raise an exception.
> I discover this issue by using maven project info report plugin (dependencies
> section)
> jdk8.patch contains a unit test expecting to have a true answer to
> isDebugPresent (as maven compiler generate debug info by default).
> jdk8jar.zip is a multimode project to reproduce the jar used in the tests.
> upgrading to bcel 6.0 SNAPSHOT works but as it's not release yet I guess I
> have to wait :p
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
