search

branflake2267 / GWT-Maps-V3-Api

GWT Maps V3 Javascript Bindings
Other
144 stars 113 forks source link

Figure out what to do with ajax loader gwt-user and gwt-dev is at 2.0.3 #162

Open branflake2267 opened 11 years ago

branflake2267 commented 11 years ago

Since the ajax loader is using gwt-user and gwt-dev 2.0.3 it creates annoying conflicts now and then. I'm wondering if I should look at updating this.

twistedpair commented 11 years ago

You can exclude those dependencies in the Maven dependency tag. I bet it will build with any forward version.

branflake2267 commented 11 years ago

Good point. If we include it as a transitive would could control that more too.

Axxiss commented 11 years ago

Any news about this? I'm using the latest GWT Maps version from Maven central and I'm stilll having this issue.

EDIT:

As a workaround adding the latest version to my project's pom removed the issue

<dependency>
    <groupId>com.google.gwt</groupId>
    <artifactId>gwt-dev</artifactId>
    <version>2.5.1</version>
    <scope>test</scope>
</dependency>
branflake2267 commented 11 years ago

Nothing new at the moment, I haven't had time to update. Thanks for sharing the workaround.

twistedpair commented 10 years ago

Just faced this problem again. Now however, with gwt-maven-plugin 2.5.1 the my project will not even compile due to incompatible compiler flags.

As such, simplest workaround is, in your consuming project POM:

<!-- Include Core gwt-maps-api --> 
<dependency>
    <groupId>com.github.branflake2267</groupId>
    <artifactId>gwt-maps-api</artifactId>
    <version>3.10.0-alpha-6</version>
    <!-- Exclude outdated gwt-dev that breaks compile -->
    <exclusions>
        <exclusion>
            <artifactId>gwt-dev</artifactId>
            <groupId>com.google.gwt</groupId>
        </exclusion>
    </exclusions>
</dependency>

For the long term fix, doing the above exclusion within the gwt-maps-api POM should also do the trick.