remove guava dependency from catalog module
This is possible because all classes in catalog module replaced by our own (or our forked version) classes. Additionally, keep guava in this module while no direct use causing build failed.
<artifactId>jsr305</artifactId>
<scope>provided</scope>
</dependency>
- <dependency>
- <groupId>com.google.guava</groupId>
- <artifactId>guava</artifactId>
- <!-- Required scope for the maven shade plugin (tools) -->
- <scope>compile</scope>
- </dependency>
<dependency>
<groupId>com.google.inject</groupId>
<artifactId>guice</artifactId>
