[
http://jira.codehaus.org/browse/MGWT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202710#action_202710
]
Richard Allen commented on MGWT-131:
------------------------------------
To elaborate on my previous comment, a pom project does not need source code to
run a GWT compile. In our case, the pom project builds a war directory, we
configure gwt-maven-plugin to use that war directory, and give gwt-maven-plugin
a GWT module to compile. The specified GWT module is on the classpath, so the
GWT compiler successfully finds it and compiles it into the war directory of
the pom project. This configuration provides lots of flexibility for a
multi-module project. Before this fix, this configuration works beautifully.
> Plugin attempts to compile projects with 'pom' packaging
> --------------------------------------------------------
>
> Key: MGWT-131
> URL: http://jira.codehaus.org/browse/MGWT-131
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Fedora 11, Java 1.6.0_16, Maven 2.2.1, GWT 1.7.1
> Reporter: Daniel Scott
> Assignee: nicolas de loof
> Priority: Minor
> Fix For: 1.2
>
>
> When the GWT compile goal is enabled for projects which have the 'pom'
> packaging type, maven attempts to compile the project and fails because no
> source code is available. The compilation should be disabled by default for
> projects which have the 'pom' packaging type.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
