At first, maven-gwt-plugin must be of 1.3.1.version, ver 1.2 that is
available in the "official" maven repository does not support
compileSourcesArtifacts tag.
The other problem is that I tried to include generic module by adding
Generic.gwt.xml in gwtmod module, but this file must be located in the
resources of the distributed library, i.e. in generic module's
resources.
Though it's a pity that I can't use relative path in the gwtmod, e.g.
telling GWT compiler to use sources from, say, ../another-project/main/
java/** path - to not to modify external library's source code and
maven configuration. And I guess this is not that bad because exported
module must be checked early by the GWT compiler for using only the
emulated part of the JRE.
On Nov 1, 11:21 am, Alex Shabanov <avshaba...@gmail.com> wrote:
> Thank you for attention for my problem.
>
> On Nov 1, 3:21 am, Jeff Larsen <larse...@gmail.com> wrote:
>
> > Put a gwt.xml file in the project.
>
> I did. It's name is Generic.gwt.xml.
>
>
>
> > define the module, then you'll be able to import your library project
> > into a gwt project.
>
> The same thing, yes I defined the module (Generic.gwt.xml), but it
> never compiles:>> [INFO] com.mysite.generic.Generic is up to date. GWT compilation
>
> skipped
>
> This results in the subsequent error in Application module because it
> uses Constants type defined in the Generic module.
>
>
>
> > ...
>
> By the way, the sources of the sample application is available, just
> do svn checkouthttp://webkit-jspf.googlecode.com/svn/trunk/tmp/maven/gwt-external-lib
> It compiles without errors if the usages of Constants type are
> commented.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment