GWT dependencies have wrong dependency scope? about gwteventbinder HOT 4 CLOSED

AFAICT, adding a provider scope wouldn't change dependency conflict resolution.

What likely happens is that you don't have a dependency on gwt-dev so you inherit the one brought transitively by gwteventbinder. And the gwt-maven-plugin won't try to "replace" it with the version matching the one its compiled against.

Indeed using a provided scope for gwt-dev would solve the immediate issue, but the real issue is elsewhere: your project not setting gwt-dev's version to 2.6.1 (you're ultimately responsible for dependency management), gwt-maven-plugin not handling the version conflicts, GWT not providing a "BOM", etc.

from gwteventbinder.

Well, on my side I'm actually using gradle and the gwt-gradle-plugin, which should take care of providing the necessary dependencies on GWT. But it might be a bug in the plugin itself, I'll investigate it further from that side.
Thank you for your help.

from gwteventbinder.

Yes, I think there's a "bug" in the gwt-gradle-plugin similar to the one in the gwt-maven-plugin of not de-duplicating gwt-dev dependencies from the project and the plugin.

That said, you're responsible for dependency management for your project, Gradle or Maven are just tools to assist you. Have a look at ./gradlew dependencies and ./gradlew dependencyInsight --dependency gwt-dev; and either declare gwt-dev explicitly with the appropriate version to override the transitive one from gwteventbinder, or exclude it, or use a dependency resolve rule, or, because gwteventbinder has no other dependency, depend only on the JAR using gwt 'com.google.gwt.eventbinder:eventbinder:1.1.0@jar'

from gwteventbinder.

Thanks for the follow up - I'll look into properly fixing this, but for now the @jar addition did the trick.

from gwteventbinder.