[
http://jira.codehaus.org/browse/MGWT-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MGWT-192:
------------------------------
Fix Version/s: 2.1.x
> gwt:soyc does not produce report
> --------------------------------
>
> Key: MGWT-192
> URL: http://jira.codehaus.org/browse/MGWT-192
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: [INFO] Maven Version: 2.2.1
> [INFO] JDK Version: 1.6.0 normalized as: 1.6.0
> [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 2.6.32.12
> [INFO] Maven Version: 3.0-beta-1
> [INFO] JDK Version: 1.6.0 normalized as: 1.6.0
> [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 2.6.32.12
> Reporter: jieryn
> Fix For: 2.1.x
>
>
> [INFO] --- gwt-maven-plugin:1.2:soyc (default-cli) @ gwt ---
> [INFO] using GWT jars from project dependencyManagement section : 2.0.3
> [INFO] WARNING: The direct use of the SoycDashboard is deprecated and will be
> removed. The preferred usage is to invoke the compiler with the
> -compileReport option, which writes the compile report directly to the extra
> directory.
> [INFO] Generating the Story of Your Compile...
> [INFO] Finished creating reports. To see the dashboard, open index.html in
> your browser.
> $ find target/extra/ | grep soyc | wc -l
> 1885
> $ find target/site
> target/site/
> target/site/soyc
> target/site/soyc/com.acme.app.gwt.Application
> target/site/soyc/com.acme.app.gwt.Application/images
> target/site/soyc/com.acme.app.gwt.Application/images/g_gwt.png
> target/site/soyc/com.acme.app.gwt.Application/images/up_arrow.png
> target/site/soyc/com.acme.app.gwt.Application/soyc.css
> target/site/soyc/com.acme.app.gwt.Application/goog.css
> target/site/soyc/com.acme.app.gwt.Application/index.html
> target/site/soyc/com.acme.app.gwt.Application/inlay.css
> So, the SOYC report is created in extra but not in the site; this somewhat
> limits the usefulness of this report generation in automated build setups.
> Please note, I ran this with Maven 2.2.1 and 3.0-beta-1 both, and both had
> the same result. Therefore, I am not inclined to think this is part of the
> drastic m3 site handling differences..
--
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
