#1000309
- Created on2011-02-28 10:48
- Reported by
- StatusInvalid
- PriorityNormal (3)
- Assigned to-
- Milestone
- Plan Level-
- Due Date-
Use guards for debug logging in the plugin source
Debug logging in the plugin source mostly does not use guards of any sort (I'm just as guilty of this as anyone). We need to add/use plugin logging preferences (separated into 3 or 4 categories?) and we must not use println's in code that is pushed to the repository.
Leave a comment
on 2011-03-25 09:11 *
By Iulian Dragos
Version set to 1.0.0-SNAPSHOT
Eclipse version set to Helios
Branch set to wip_experiment (2.9)
Updating tickets (#1000238, #1000326, #1000331, #1000264, #1000298, #1000314, #1000315, #1000325, #1000329, #1000333, #1000277, #1000209, #1000210, #1000288, #1000299, #1000300, #1000301, #1000305, #1000309, #1000310, #1000327, #1000270, #1000292, #1000293, #1000294, #1000295, #1000297, #1000303, #1000304, #1000312, #1000320)
on 2012-01-27 13:58 *
By skyluc
Type set to Enhancement
Version changed from 2.0.0-beta1 to 2.0.0-final-29
Eclipse version changed from Helios to All
Assigned to changed from lindydonna to -none-
Component changed from None to Eclipse
Milestone changed from Helium to Enhancements
Permission type changed from None to Public
