Clean up the processor's dependencies slightly, and generate a shaded jar #63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From https://github.com/google/auto/tree/master/common#processor-resilience
This is probably a good idea in general to follow - the config here is an attempt to combine the various dependencies of the processor, so that if another processor in a gwt project happens to use a different version of any of them, there won't be any conflicts.
Note that there are exclusions here, like vue-gwt core, and various jsinterop/elemental2 jars.
There are other benefits here too, like removing .java files from the classpath, so that the j2cl-maven-plugin won't think that those jars also need to be transpiled.
Finally, auto-service was mistakenly added as a scope=compile dependency, when it only is needed at compile time. As a result of this, I discovered that there is an implicit dependency on auto-common, so I added that directly.