Hi to all!
A simple question (kinda related to bug 4242): how do you manager "dirty" code? Consider this: you are working on a defect, involving lot of fixes to different methods / classes.. and you notice that a method you're working on is dirty (i.e., does a duplicated logic, use deprecated code...). Do you fix it or leave as it is? I feel it should be changeable - of course, only after a unit test is created. And, if you modify it, do you insert a new issue - or something similar?

And what about project style? If you modify a method that doesn't conform to checkstyle rules, do you make it comply with the project rules?

Regards,
              Andrea

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to