You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Zlika (JIRA)" <ji...@apache.org> on 2015/06/30 13:49:05 UTC
[jira] [Commented] (MSHARED-409) maven-shared-jar fail to analyse
jar containing "new" jdk8 code
[ https://issues.apache.org/jira/browse/MSHARED-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608162#comment-14608162 ]
Zlika commented on MSHARED-409:
-------------------------------
Any update on this annoying issue?
BCEL 6 is still a SNAPSHOT version, but maybe it would be possible to use this Findbugs version of BCEL as a drop-in replacement:
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>bcel-findbugs</artifactId>
<version>6.0</version>
</dependency>
> maven-shared-jar fail to analyse jar containing "new" jdk8 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
> 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)