jkozlov

FYI: it is impossible to use `guava` and `java.xml.ws` modules simultaneously: ``` module foo { requires com.google.common; requires java.xml.ws; } ``` This code will not compile because there is a...

Update to my previous comment. It is not impossible, however, this requires exclusion of jsr305 dependency: ``` com.google.guava guava 25.0-jre com.google.code.findbugs jsr305 ```

JSR-305 has a common package with Common Annotations which is a platform module in Java 9-10 (`java.xml.ws.annotation`). In Java 11 it is not a platform module anymore, but it still...

@garretwilson Please see [this thread](https://github.com/google/guava/issues/3198). The only remaining annotation is `javax.annotation.ParametersAreNonnullByDefault` which is used only in `package-info.java`. Any ideas how to get rid of it without breaking static analysis in...

I definitely like the second option the best: - It solves the problem with empty arrays. - Exact types give more information to viewers (e.g. make `int[]` vs `byte[]` arrays...

I created #30. I looked at attributes providers. For me, they don't look like a suitable solution for this (but I may be wrong). I think we need a new...

`FluentIterable.of(E, E...)` still doesn't have `@SafeVarargs`

It's worth mentioning that if we add `module-info.java`, all packages will not be open anymore.

@jbduncat Yes, exactly. And also private members of public classes.

All Guava packages should be closed because as @jbduncan said the dependence on class internals is a bad practice. If someone **really** wants to access the internals, they can use...