El mar, 17-07-2007 a las 17:09 +0100, Nigel Magnay escribiÃ³:
> On 17/07/07, Mark Phippard <firstname.lastname@example.org> wrote:
> On 7/17/07, Nigel Magnay <email@example.com> wrote:
> > Mostly things work, but sometimes the workspace seems to 'go
> bad' (starting
> > a new one seems to help). For example, if create a file in
> a project, say,
> > /WEB-INF/classes/properties.xml, and both the directories
> > and the file are new, if I right-click on the project and do
> > the list of files I can choose from shows only 'WEB-INF'.
> > checkins will then show each new directory as if it had just
> appeared (where
> > I'd expect it to show all of them).
> classes folder is usually in ignore list by default. I would
> recommend versioning that folder if this is a typical web
> project as a
> build process might blow away the .svn folders. Usually you
> can put
> the .xml files in a source folder and the build will copy them
> classes. That way just version them in the source folder.
> It is?! This isn't target/classes BTW, this is
> src/main/webapp/WEB-INF/classes. I now can't remember if all the files
> were under classes or not - is there a way of *un*-ignoring it (and
> wouldn't it always ignore files, rather than marking each successive
> directory as new) ? We tend to store rather a lot of spring
> configuration under there,..
Storing source in an output folder is not recommended. Personally I use
a Maven-like hierarchy and store the source code under src/main/java and
those files under src/main/resources, just as Mark suggested.
Javier Kohen <firstname.lastname@example.org>
ICQ: blashyrkh #2361802
Received on Tue Jul 17 18:28:30 2007