I can remember this issue been discussed many times on this forum, e.g. http://groups.google.com/group/gwt-maven/browse_thread/thread/6d27875ae2af832a/26600b80956c54b2
but I guess there just hasn't been an agreement over which solution would be the best one. Cheers Mirko 2009/1/21 Jamie Whitehouse <[email protected]>: > > It's been a while since I've upgraded my projects build, and since I > had a break I thought I'd try the latest plugin version, 2.0-beta26. > The previous version I was using was 2.0-beta15 with my patch for in > JVM classpath assembly and compilation to work around the windows path/ > input line issues. See file at > http://gwt-maven.googlegroups.com/web/CompileUsingJavaMojo.java > and discussion thread at > http://groups.google.com/group/gwt-maven/browse_thread/thread/f2a11609b150b7d8/3a60442727830d09 > . > > I noticed that there's been a lot of effort put into fixing this and I > was hopeful for beta26, but I still have the same issue. Has anyone > else on Windows experienced this path problem with this release? Is > there any chance of the previous patch being applied with a new > release? Should I continue to patch my local version? > > Any input is appreciated. > Jamie. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
