Robert Scholte wrote: > > It looks like it's a Stack buffer overflow / overrun. >
Good find! I wonder then if it would have something to do with the length of the command line. Back in April 2009, on http://jira.codehaus.org/browse/MGWT-49 the Codehaus JIRA , Nicolas de Loof wrote: The change was required to bypass command line length limitation on Windows. Running in a script breaks where dependencies introduce classpath more than ~4000 chars The fix is to run as a forked process, with no shell to parse the command. This seems to have ugly side-effect on Unix-based systems. last-chance attempt : use the "classic" plexus Commandline with a Shell on unixes and the "custom" no-shell on Windows. I don't really understand what it means, though; and it appears that the problem was fixed back then, so... I suspect that the problem is not with my POM, but with the plugin itself. What is the process for getting these things looked at? -- View this message in context: http://old.nabble.com/Mysterious-error-during-gwt%3Acompile-tp27511167p27513873.html Sent from the mojo - user mailing list archive at Nabble.com.
