[ 
https://issues.apache.org/jira/browse/JCLOUDS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644469#comment-14644469
 ] 

Zack Shoylev commented on JCLOUDS-975:
--------------------------------------

You can add this dependency to figure out where the problem is:

<dependency>
    <groupId>com.google.code.findbugs</groupId>
    <artifactId>jsr305</artifactId>
    <version>1.3.9</version>
</dependency>

This will alert you that one of the tests is using a method call but does not 
check the returned value. Adding an assert will fix that, and the dependency is 
not needed.

> compilation failures with Guava 19.0-rc1
> ----------------------------------------
>
>                 Key: JCLOUDS-975
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-975
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>    Affects Versions: 2.0.0
>            Reporter: Andrew Gaul
>            Assignee: Zack Shoylev
>              Labels: openstack-nova
>
> Seen when running {{mvn clean test-compile -Dguava.version=19.0-rc1}}:
> {noformat}
> [INFO] Compiling 124 source files to 
> /home/gaul/work/jclouds/apis/openstack-nova/target/test-classes
> warning: No processor claimed any of these annotations: 
> org.testng.annotations.AfterClass,org.jclouds.rest.annotations.ResponseParser,org.testng.annotations.DataProvider,org.testng.annotations.BeforeClass,org.testng.annotations.BeforeMethod,org.testng.annotations.Test,org.jclouds.rest.annotations.SelectJson,org.testng.annotations.AfterMethod,org.testng.annotations.BeforeTest,javax.ws.rs.Consumes,org.testng.annotations.BeforeGroups
>    
> error: cannot access CheckReturnValue
>   class file for javax.annotation.CheckReturnValue not found
>   Consult the following stack trace for details.
>   com.sun.tools.javac.code.Symbol$CompletionFailure: class file for 
> javax.annotation.CheckReturnValue not found
> {noformat}
> We should investigate this before Guava 19.0 releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to