Le 16 nov. 2012 17:59, "Daniel Kurka" <[email protected]> a écrit : > > Hi Thomas, > > I have been out on devoxx and haven`t had time to cast a vote yet. > > I think its a good idea to go with a separate package like src/main/super for super sourcing. > > Why are we thinking of moving resources out of src/main/java,
Depends where you come from ;-) Maven users where (almost) ALL complaining when GPE didn't see their files in src/main/resources. If you think of src/main/java as the set of files processed by javac, then gwt.xml, ui.xml and the like should obviously go to resources (or some other, GWT specific, folder). > what is the main advantage here? Separation of concerns (even though java sources will end up processed the same as gwt.xml, they're also processed by javac, and generally not filtered), filtering, freedom (e.g. one might want to put the gwt.xml at the root of resources and define <targetPath> to relocate them in the appropriate package in the generated JAR, it'd make navigation easier in Eclipse – IntelliJ has a package presentation which makes this pointless –; I could see me doing that for super-sources in case I have a single module in my lib) Honestly, it's mostly a matter of taste, and both would work and in 99% of the cases, but src/main/resources feels more "mavenish" (note: I was a proponent of src/main/java some time ago, I now believe it was mostly due to tooling). -- 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.
