Maven JAR analyser unable to read target byte code about lambda-behave HOT 10 CLOSED

Thanks for the bug report @karianna - do you have a sequence of steps I could use to reproduce this issue? If not even a description of what was happening or what you were doing at the time would be helpful.

from lambda-behave.

Yeah, looks like the only version of BCEL which supports Java 8 is in findbugs - https://twitter.com/wendigo/status/485786418523156480

from lambda-behave.

Argh, of course, sorry - just run mvn clean compile site I was using Maven 3.2.2, but I suspect you might see it with 3.2.1 as well.

from lambda-behave.

Fair enough, I guess close with Won't Fix :-)

from lambda-behave.

Maybe worth leaving the issue in place to track the bug and once they've released a fix can re-test then.

from lambda-behave.

Maybe fixed soon:
https://twitter.com/rafaelonjava/status/485803028101201920

from lambda-behave.

Any update on this?

from lambda-behave.

Got the same problem. I ended up in replacing the bcel 5.2 dependency with the bcel-findbugs V6.0 version which does have support for lambda functions.
This is what i did in my pom-file:

<build>
    <plugins>
...

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-project-info-reports-plugin</artifactId>
    <version>2.8</version>
    <dependencies>
        <dependency>
            <groupId>org.apache.maven.shared</groupId>
            <artifactId>maven-shared-jar</artifactId>
            <version>1.1</version>
            <exclusions>
                <exclusion>
                    <groupId>org.apache.bcel</groupId>
                    <artifactId>bcel</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>com.google.code.findbugs</groupId>
            <artifactId>bcel-findbugs</artifactId>
            <version>6.0</version>
        </dependency>
    </dependencies>
</plugin>

...

    </plugins>
</build>

from lambda-behave.

Thank you sdhaene this helped me.

from lambda-behave.

@russray2008 this should be fixed in the 0.4 release btw.

from lambda-behave.