As a follow-up to this discussion, I went ahead and logged an
enhancement to the gwt-maven-plugin to automatically resolve and
download the source jars[1]. It seems like it will be included in the
next release.
[1] - http://jira.codehaus.org/browse/MGWT-170
On Thu, Feb 11, 2010 at 1:24 PM,
We also use the Maven sources JAR approach. The .class and .java do
NOT have to be in the same JAR file. The GWT compiler will just need
the sources JAR on the classpath, which you can accomplish via Maven
dependency management, as you have stated.
The only problem I found using the Maven
Yes, they have to be in the same jar, so you have to include this
lines in your pom.xml:
build
.
resources
resource
directorysrc/main/java/directory
/resource
resource
I acknowledge that the source needs to be available for the gwt
compiler but I still question if the source needs to be in the same
jar as the compiled endstates you'd ship to a client. Is there
documentation that states the requirements (location/conditions) for
providing source code to the gwt
I currently have a GWT app that I'm looking to break into separate
modules. The build system is currently Maven2 and utilizing the gwt-
maven-plugin[1]. When reading over the documentation on how to do
this, I wonder what exactly are the requirements around the source
code for a module being
Yes.. the GWT compiler needs to have available the java source code to work
2010/2/4 Micah mkwhita...@gmail.com
I currently have a GWT app that I'm looking to break into separate
modules. The build system is currently Maven2 and utilizing the gwt-
maven-plugin[1]. When reading over the
