[
http://jira.codehaus.org/browse/MGWT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey De Smet updated MGWT-266:
----------------------------------
Attachment:
MGWT-266_gwt_run_should_include_compileSourceArtifact_sources_in_classpath.patch
Attaching patch with fix for this issue.
The patch moves the addCompileSourceArfitacts(cmd) method up from
CompileGwtMojo, and reuses it in the RunGwtMojo.
I've tested the patch and it works for gwt:run.
> compileSourcesArtifacts ignored by gwt:run
> ------------------------------------------
>
> Key: MGWT-266
> URL: http://jira.codehaus.org/browse/MGWT-266
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.1.0-1
> Environment: All
> Reporter: Tolga Tarhan
> Attachments:
> MGWT-266_gwt_run_should_include_compileSourceArtifact_sources_in_classpath.patch
>
>
> The "Writing a GWT library" page at
> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/library.html describes
> how compileSourcesArtifacts can be used in a GWT project to pull-in a source
> package of a non-GWT library to make the GWT compiler happy. This allows the
> use of non-GWT libraries, or libraries whose source you do not want to
> provide in the main jar file.
> However, since this option is ignored by the gwt:run target, it's impossible
> to use development/hosted mode when your project is setup in this fashion.
> This makes the compileSourcesArtifacts option fairly weak, since you can only
> use the mechanism described on the page above if you always compile, and
> never use development/hosted mode (which is very contrary to GWT development).
--
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
