On Mon, Feb 9, 2009 at 9:47 AM, logicpeters <[email protected]> wrote:
> > "Note that the > war directory is not only for compiler output; it is also intended to > contain handwritten static resources that you want to be included in > your > webapp alongside GWT modules (that is, things you'd want to version > control)." > > I'm not following... Do you mean for us to include these static > resources in the compiler output directory and maintain this directory > under source control (with generated code alongside static source, > such as index.html and css files)? That seems like a bad idea to me. > Not exactly... the compiler output directory is considered to be "/war/<moduleName>".... NOT "/war" itself really. In other words, you can put whatever resources you want into the top-level war directory, the compiler generated files will always be put into the moduleName subdirectory under this, so as not to conflict. Why not enforce the standard J2EE project path (see Sun's blueprints), > and maintain these files under /src/conf. > We might have to look into this. Scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
