Thanks for the tip Thomas, I'll check it out. The downside of this is that I now need to update my ant build file that was created using webAppCreator to manually copy these resources prior to running "ant hosted" or "ant war". I agree that while the GWT 1.6 project structure is a huge improvement, the use of the "war/WEB- INF/classes" directory in the source directory path doubling up as the default compile output path is a little unclean.
On Jun 29, 3:15 pm, Thomas Broyer <[email protected]> wrote: > On 29 juin, 20:51, Jeremy Cohen <[email protected]> wrote: > > > I'm using GEP Eclipse 3.4.0 with GEP 1.0.1v200905131143 > > > I created a GWT project using GEP. The default output folder is > > <project>/war/WEB-INF/classes. I need to have some properties files in > > my classpath and I usually place them under the WEB-INF/classes > > directory (for example log4j.properties). Since GEP users <project>/ > > war/WEB-INF/classes in the main "source" directory structure, and not > > a separate build output directory, when I do a rebuild, it cleans out > > the <project>/war/WEB-INF/classes directory and I lose my source > > properties and config files. Is there any recommendation for such a > > usecase? > > Er, put them in the root of your project's source folder; they'll > automatically be copied into WEB-INF/classes. > > (note that this has nothing to do with the GEP AFAICT, if you want to > blame something, blame GWT 1.6+) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
