Elliotte Rusty Harold
Elliotte Rusty Harold
This needs a JIRA issue
Right now we have several convergence errors: [INFO] --- maven-enforcer-plugin:1.4.1:enforce (default) @ com.google.cloud.tools.eclipse.util --- [WARNING] Dependency convergence error for p2.eclipse-plugin:com.google.guava:20.0.0 paths to dependency are: +-com.google.cloud.tools.eclipse:com.google.cloud.tools.eclipse.util:0.1.0-SNAPSHOT +-p2.eclipse-plugin:com.google.guava:20.0.0 and +-com.google.cloud.tools.eclipse:com.google.cloud.tools.eclipse.util:0.1.0-SNAPSHOT +-p2.eclipse-plugin:com.google.guava:15.0.0.v201403281430 [WARNING]...
I think fixing #1493 would resolve the Guava issues. Also see https://github.com/google/google-http-java-client/issues/348
I'm hesitant about preventing an end user from removing a facet. I'm not sure WTP is actually doing the right thing here. However perhaps removing one should remove the others?...
I'm a weak -1. I prefer to avoid new discrepancies with ANSI SQL and also like to avoid multiple ways to do things.
This isn't a generic zip plugin. It's specifically designed to create JLink images which happen to be zip files, I think. Do the runtime images still work if one adds...
The detailed design is very good. Thanks. Can/should this be ported to an RFC so it's in the git repo and doesn't rely on google docs accounts that might go...
No, I just need to decide whether I want to merge this or not.
I propose option 3: catch and handle the exception, or maybe just fail the query, but definitely catch it. Don't remove the checks.
@dependabot rebase