Should we or should we not check in the classes folder in WEB-INF directory into SVN?

Subversion is best for managing changes to plain text files, such as source code. An svn diff won't help if you're doing it on, say, a JPG image or a compiled Java . Class file.

Subversion is best for managing changes to plain text files, such as source code. An svn diff won't help if you're doing it on, say, a JPG image or a compiled Java . Class file.

You can use svn:ignore on anything that you always want to avoid checking into a subversion repository, such as WEB-INF/classes or WEB-INF/lib or your maven . /target directory.

Ok. I will use svn:ignore. – Vatsala May 10 '10 at 10:49.

As a rule of thumb, you should only check the source code into your version control system, and ignore the binaries. The . Class files can be built from the source code, so they don't really provide any extra information - and it is trivial to re-create them if you need .

Class files.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.