> It comes without saying (for me at least) that Java sources would go into > src/main/java and "public resources" (i.e. the things within **/public/**, > e.g. the CSS and image files from the themes) into src/main/resources >
I agree with this. > everything in src/main/java > super-sources in src/main/resources > The major drawback to this is that putting everything in src/main/java makes it more difficult to re-use filtering configuration for maven-resources-plugin. Placing the super-sources in src/main/resources may also cause filter-related "surprises." > everything in src/main/resources > I suspect that this may cause problems/annoyances because project.build.sourceDirectory points to src/main/java by default. This also is subject to potential filtering issues. everything in src/main/resources > super-sources in src/main/super (or gwt-super, or some other name, let's > discuss that later as I suspect it's a bikeshed) I like the idea of having the super-sources in a separate source directory. Objections to putting everything in src/main/resources are noted for option #2 above. > Also feel free to propose a fourth alternative. > I'd propose keeping non-super sources in src/main/java, public resources in src/main/resources, and super-sources in src/main/super. As different as GWT projects may be from other "normal" Java projects, I think there's still value in keeping to convention if it's possible and sensible to do so. -Abraham -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/FHCWDOv2imkJ. 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.
