Build are failing about clutz HOT 7 OPEN

What's the status on this? I've noticed that clutz builds have been failing on CircleCI for about 6 months. Looks like the most recent successful build is https://circleci.com/gh/angular/clutz/563. I'd like to use clutz to convert a Closure project to more modern web frameworks, but I'm not sure whether to use the latest successful build from 6 months ago or to try to get a build working from master.

from clutz.

Internal issue created: b/148431526

from clutz.

@mprobst Is this something we can reproduce at all?

from clutz.

Yes, I can reproduce. I think the problem is as kwiva writes that the Guava version referenced in build.gradle does not match what we're using internally. 28.2 should actually include the missing splitToStream method though:

https://github.com/google/guava/blame/master/guava/src/com/google/common/base/Splitter.java

from clutz.

kwiva, can you talk more about how you use Clutz? One option we're considering is archiving the project completely because it's difficult for us to publish and we don't think there are many users.

from clutz.

The problem is you are depending on https://search.maven.org/artifact/com.google.javascript/closure-compiler which is a "shaded" JAR, where all the dependencies (e.g. Guava) are re-packaged inside it. The shading is supposed to rename the deps to prevent conflicts, but it seems this hasn't been configured properly for closure-compiler, so the upshot is that its outdated version of Guava (25.1-jre) is on the classpath no matter what, and Gradle can't override it.

The solution is replace your closure-compiler dependency with the unshaded version, e.g. com.google.javascript:closure-compiler-unshaded:v20200517, then force the Guava version in build.gradle:

compile ('com.google.guava:guava:28.2-jre') {
  force = true
}

😫 Debugging nonsense like this reminds me why I gave up Java development.

from clutz.

As I commented a bit upthread we (the Clutz maintainers) are not great at these kinds of issues and have discussed archiving the project. If you use Clutz, could you comment on #1006 ?

from clutz.