OK, I answered my own question, at least as far as item #1, with some help from http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html#DevGuideAutomaticResourceInclusion
It seems that either approach will work. Having the css in the public package will result in it automatically being included, as long as the modules gwt.xml file references it. Otherwise, I need to include the module's css file in the war directory of the inheriting project, and have that project's html file link to it. I guess that would also give me the ability to more easily override the styling, plus it gets around Eclipse's reluctance to create a package level named "public" (although it was nice enough to use it if I created it externally). I still wonder about #2 - if there is a way to jar it without resorting to two command-line jar commands ... On Nov 13, 1:37 pm, Steve C <[email protected]> wrote: > In GWT 1.5, I would put the module css file in the public package. In > 1.7 the preferred approach is to put it in the war directory. I > haven't tested to see if the public package concept still works. > > If I wanted to have a project as a module, I could then jar the whole > thing, and the project inheriting the module would find the css file > in the public directory. > > 1. To create a module for 1.7, do I have to add the relevant css file > to the new project's war directory, or do I back up and create it in a > public package a la 1.5? (or do I do something else, like add the war > directory to the module's jar file)? > > 2. Is there a tool in the Eclipse plugin to create/export a module jar > file, or do I have to do that manually? > > 3. Is there a structure for the module war file other than that the > root starts the package structure (e.g., a src folder, a bin or > classes folder, etc.)? -- 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=.
