I think perhaps we should support extensible categories of output files (for
example I think it might be useful to split out things expected by the build
system from other non-runtime output, since the build system output can't
change names or formats while human-readable files could).  Maybe -dir
SERVING=www -dir CONTEXT=... etc.  By default if nothing but -out is
supplied (or if no "master output format" option is supplied), everything
defaults as it does now.  If -war dir is supplied, that creates a different
set of defaults for all these categories, but can still be overridden by
doing something like -war war -dir EXTRA=myCustomExtra.

I think it might be useful to have some form of variable substitution on
these, so you could include the module name at different places in the path
as appropriate.  So, for backwards compatibility EXTRA's default could be
{outDir}/{moduleDeployTo}-aux.

-- 
John A. Tamplin
Software Engineer (GWT), Google

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to