The thing I'd not like to lose, is "live-edit" capability. ie: changes
take effect with a simple page reload in HostedMode (and also Restart
Server button in 1.6).
I think GWT provides enough options to make things work, but it's
harder than it should be. If I had a magic wand though, I'd say having
"war dir overlay" parameter would make life much simpler. If it could
do this, and still detect changes to the source, that would be sweet.
You'd just set -warOverlay /src/main/webapp -war /target/$
{project.build.finalName} That actually wouldn't effect existing users
one bit. Actually... maybe I should work on a patch and submit it to
GWT, you never know ;-)
On Apr 16, 2:00 pm, Matt Bishop <[email protected]> wrote:
> One of the big wins with Maven is the "rigid" directory structure,
> where source files of all stripes are in src/ and build outputs are in
> target/. It's good practice because it doesn't allow for intermingling
> source files and build files.
>
> The new GWT war/ dir next to src/ problematic because you have to be
> careful how you clean up. I can see many an "aaargh!" being screamed
> out in the early morning hours when a tired developer discovers a bug
> in her ant script, or when he trashes the war/ dir accidentally.
>
> I would much rather have seen src/java and src/war (better yet, src/
> webapp) and the HostedMode compiler would copy src/webapp to war/
> before compilation. It would be a whole lot safer and wouldn't really
> cost that much, even for large projects with a whole lotta webapp/**
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" 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/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
