maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zlika (JIRA)" <>
Subject [jira] [Commented] (MSHARED-409) maven-shared-jar fail to analyse jar containing "new" jdk8 code
Date Tue, 30 Jun 2015 11:49:05 GMT


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:

> maven-shared-jar fail to analyse  jar containing "new" jdk8 code
> ----------------------------------------------------------------
>                 Key: MSHARED-409
>                 URL:
>             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,
> 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).
> 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

This message was sent by Atlassian JIRA

View raw message