search

gwt-plugins / gwt-eclipse-plugin

GWT Eclipse Plugin Documentation
http://gwt-plugins.github.io/documentation/
Eclipse Public License 1.0
112 stars 48 forks source link

runClasspathExcludes seems to be disregarded #387

Open JanecekPetr opened 6 years ago

JanecekPetr commented 6 years ago

I'm using the org.codehaus.mojo.gwt-maven-plugin plugin in version 2.8.2.

This is my configuration:

<configuration>
    <module>com.mycompany.myproject.gwt.App</module>
    <extraJvmArgs>-Xmx2G</extraJvmArgs>
    <runTarget>app</runTarget>

    <runClasspathExcludes>
        <runClasspathExclude>storm-core-1.0.1.jar</runClasspathExclude>
    </runClasspathExcludes>
</configuration>

the interesting part is the runClasspathExclude. When I run GWT Development Mode, the jar is not excluded from the war classpath :(.

This makes the JAR appear twice on the classpath which is something that it explicitly guards against:

Found multiple defaults.yaml resources. You're probably bundling the Storm jars with your topology jar. [jar:file:/C:/Data/Maven%20Repository/org/apache/storm/storm-core/1.0.1/storm-core-1.0.1.jar!/defaults.yaml, jar:file:/C:/Git/myproject/myproject-ui/target/myproject-ui-2.0.5-SNAPSHOT/WEB-INF/lib/storm-core-1.0.1.jar!/defaults.yaml]

Is there any workaround I can do to exclude the jar?

branflake2267 commented 6 years ago

This issue I think goes to the GWT Maven plugin. I'd probably suggest trying to use the newer gwt maven plugin by tbroyer. If the IDE is supposed to look at this and do something, then it would be a IDE launcher issue. I would open up the launcher and adjust the classpath manually after the IDE maven update has run.