New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Java 8 #3
Comments
|
Note: After some further debugging, project-info-reports-plugin is pulling bcel in as a transitive dependency. Since clirr is declaring the dependency, it would override the project-info-reports-plugin. |
|
Does anyone know bcel's release plan? On Tue, Aug 4, 2015, 11:32 AM AndrewJCarr notifications@github.com wrote:
|
|
From their mailing list: http://mail-archives.apache.org/mod_mbox/commons-dev/201507.mbox/%3C20150719220950.Horde._yMpE-t8WTgygtKF5weW7Q1%40secure46.inmotionhosting.com%3E It looks like they're trying to get it shipped soon. |
|
any news from this as bcel has released its version https://github.com/apache/commons-bcel/releases |
|
Replacing the explicit <dependency>
<groupId>org.apache.bcel</groupId>
<artifactId>bcel</artifactId>
<version>5.2</version>
</dependency>with <dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>bcel-findbugs</artifactId>
<version>6.0</version>
</dependency>did the trick for me (see RichardWarburton/lambda-behave#31 (comment)). I wasn't able to find a non-RC version of above apache commons-bcel. Any chance that Java8 compat. will make it into 2.8? |
|
May I ask if this is fixed with release 2.7? Apache Wicket (https://github.com/apache/wicket) uses clirr-maven-plugin and 8.0.0-M1 is going to be released, soon. It would be nice if we can update the plugin to get compatibility for Java 8, because this is also a requirement for Wicket 8. 👍 Corresponding ticket: https://issues.apache.org/jira/browse/WICKET-5836 |
|
Hi @klopfdreh On the XWiki project (http://xwiki.org) we've switched to using revapi, see http://massol.myxwiki.org/xwiki/bin/view/Blog/ByeByeCLIRRWelcomeRevapi |
|
Hi @vmassol - thanks a lot for that hint - we are going to have a look at it. |
|
While this is in progress, is there any way to force v2.7 of the plugin to use com.google.code.findbugs:bcel-findbugs:6.0 rather than org.apache.bcel:bcel:5.2? I can include an extra dependency on the google version, but there's no tag within in the Maven model to allow me to exclude the apache one. |
|
+1 to Mahoney's question. |
switch to a java 8 compatible version of bcel, fixes #3
|
Cool! Note that even though this issue is closed, it doesn't add support for Java 8 as the issue title claims ;) It just makes it not fail if you're under java 8 but use java 7 constructs. As I mentioned above if you're look for java8 support consider using revapi or japicmp (see http://massol.myxwiki.org/xwiki/bin/view/Blog/ByeByeCLIRRWelcomeRevapi). |
Relevant issues: + mojohaus/clirr-maven-plugin#3 (fixed in 2.7) + mojohaus/clirr-maven-plugin#7
I'm uplifting a project to Java 1.8 and the clirr-maven-plugin is dying on me in the reporting section with the error:
Stack trace: Gist
It appears that the Apache BCEL dependency needs to be updated to version 6.0 when it gets released.
I also downloaded the BCEL 6.0 snapshot version in consideration for release, managed the dependency version, and it succeeded to generate the report.
The text was updated successfully, but these errors were encountered: