[
http://jira.codehaus.org/browse/MGWT-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-44.
-------------------------------
Assignee: nicolas de loof
Resolution: Fixed
Fix Version/s: 1.1
Applied on all forked-command based goals (compile, run, i18n)
Woks fine, thanks a lot !
For info, the "standard" PlexusUtils commandLine always run commands using a
shell, so it doesn't solve the "windows command line lenght" issue.
I had to hack the plexus.cli.Shell to execute java with plexus-utils
infrastructure (your patch hase some synchronisation issue, take a look at
CommandLine.execute)
> gwt:run mojo fails on windows because the classpath is too long for the
> command line.
> -------------------------------------------------------------------------------------
>
> Key: MGWT-44
> URL: http://jira.codehaus.org/browse/MGWT-44
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Windows XP, Vista, Vista 64
> Reporter: John Vliet
> Assignee: nicolas de loof
> Fix For: 1.1
>
> Attachments: ProcessLauncher.patch
>
>
> When the dependency list is large (most typical from server side
> dependencies) the classpath variable's 8k limit is exceded. Using the
> JARBOOTER strategy also fails because the Hosted Mode browser only scans the
> JVM and gwt.booter.jar for gwt module resources.
> Using ProcessBuilder resolves this (tested up to 12k classpath). attached is
> a patch that works for GWT 1.6
--
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
