+1 I think we should create two packages:
1. A binary distribution for runtime use. 2. An SDK version for development use. This has class files compiled with debug information and source code so people can do source level debugging. Arthur Ryman, IBM Software Group, Rational Division blog: http://ryman.eclipsedevelopersjournal.com/ phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: [EMAIL PROTECTED] Lawrence Mandel/Toronto/[EMAIL PROTECTED] 01/07/2007 11:21 PM Please respond to [email protected] To [email protected] cc Subject Re: source and line number info in stack traces Jeremy, Does adding this debug info have any performance repercussions at runtime? If so, perhaps long term we should build two sets of jars for releases. Lawrence "Jeremy Hughes" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 01/05/2007 05:56 AM Please respond to [email protected] To [email protected] cc Subject source and line number info in stack traces Currently we don't have debug info in our classes when building using Ant. To help our users who use the binary distribution debug problems themselves, I propose we add debug="true" and debuglevel="vars,lines,source" attributes to all javac tasks in our build.xml files. In fact I have the change ready to check in, so will do that. If anyone feels strongly enough (!) we can back it out. Cheers, Jeremy --------------------------------------------------------------------- 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]
