I like debug on. When a customer has an issue that needed debugging level information it is tricky enough that we have to guide them on how to turn on debugging and other particulars for our software and then try again. Now, I'd have to either change our build to include debug jars instead of plain jars, bleh. And I would hope that the debug jars not be called *-debug, because I'd want to rename those to the normal name. And what about manifests? A commons component that depends on other commons jar would need to depend on the right debug or non-debug versions. More room for errors, more headaches.
What the argument for debug off? Saving disc space? Thank you, Gary > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of James Carman > Sent: Wednesday, March 19, 2008 6:38 AM > To: Jakarta Commons Developers List > Subject: [DISCUSS] Distribution jars and debug compiler setting... > > All, > > We were discussing in another thread about the merits of the > dependencies report from m2 when I noticed our report that tells us if > the dependency was compiled with debug turned on or not (this should > be part of the default m2 report if it isn't already). Anyway, I was > thinking that maybe our distributions should be compiled with debug > turned off by default and we should also have a version that has it > turned on for folks to download if they need it. Either way, we > should probably offer two different versions. I don't really care > what the default is. We could use maven classifiers to distinguish > between the two. Thoughts? > > James > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
