It just seemed to me that I commented out a line of code to check the reasons and finished checking the code back to the repository with comments.
eg. I set the rule to work in Eclipse RCP on one line. When developing a new function, I commented on this line, so the rule is not set.
After a couple of hours, the new function was completed and ready for transfer to SVN. While I changed a lot of things, I usually just double-check my changes, synchronizing with the repository (in Eclipse) and looking at all the classes that perform some kind of reasonableness check (i.e.: asking myself if I really touched this class ?). But I do not check every line.
So, in this case, I did not remember the commented line, and it got into SVN.
Now I was wondering if I could find some kind of automatism to prevent such errors. I was thinking of creating a code template or task tag and marking a commented line. And then check this task tag in the pre-commit svn binding.
Iโve been searching Google for some time, but couldnโt find anything. Does anyone know a way to do this? Or maybe something that is close to this and just needs minor changes to achieve what I'm looking for?
source share