[
http://jira.codehaus.org/browse/MGWT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174341#action_174341
]
nicolas de loof commented on MGWT-55:
-------------------------------------
Does this mean that in your setup, you compile GWT classes in WAR project "W"
using source code from another project "Y" ?
root POM
|_ project Y
| \_ src/main/java
\_ project W
|_ src/main/java
\_ src/main/webapp
In such case, you just CAN'T build the project W without running in a reactor,
do you ?
I can understand the idea of using sources from sibling project for
productivity, but your project Y should be set to include sources in the JAR as
any GWT-library is required to do. With such configuration, the sibling project
target/classes would contains the sources and during reactor build they would
be accessible to compiler
> Consider (re)sourcesOnPath when checking for required compilation
> -----------------------------------------------------------------
>
> Key: MGWT-55
> URL: http://jira.codehaus.org/browse/MGWT-55
> Project: Maven 2.x GWT Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Stefan Hübner
> Priority: Minor
> Attachments: MGWT.patch
>
>
> In our multi-module project CompileMojo doesn't notice changed sources, if
> those sources reside in a module which is a sibbling to the WAR module. So
> the application won't get recompiled. This is because
> {{CompileMojo#compilationRequired()}} doesn't respect {{sourcesOnPath}} and
> {{resourcesOnPath}}.
> Attached is patch to fix this behaviour. It has been tested on our projects.
> Cheers!
> Stefan
--
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
