We have had about 8 different approaches to fixing this - but no one
that volunteered to be the owner of it.  I don't have a Windows
machine, so it shouldn't be me.  I have asked for contributors many
times in the past - it's more than a patch, though those are very much
appreciated - it really needed an owner.  At this point I am going to
concentrate on maintaining GWT-Maven with it's current setup/approach/
features, and not change it drastically, because I am planning to
Merge with the Mojo gwt-maven-plugin anyway - when I get a chance
(getting closer to being able to focus on that).

Nicolas claims they have solved the Windows long classpath issue
there, but I am not sure about the details.

Seems like it might still be an issue based on threads I read, and all
the different approaches I have seen have one or another drawback.

I think ultimately something along the same lines as what Surefire
does will be needed:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/class-loading.html

But I am not sure that works with Embedded Tomcat or Jetty:
http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/c9206ea6850ecddb/ab4be5bfbd7b8d12?lnk=gst&q=nicolas#ab4be5bfbd7b8d12


On Jan 21, 5:02 pm, Jamie Whitehouse <[email protected]>
wrote:
> 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 
> athttp://gwt-maven.googlegroups.com/web/CompileUsingJavaMojo.java
> and discussion thread 
> athttp://groups.google.com/group/gwt-maven/browse_thread/thread/f2a1160...
> .
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to