Well, IMHO the full debug info should stay there.
After you download joda, you will most probably spent quite some time
developing with it (before deploying your app).
When exceptions in Joda occur they are most probably your own fault
(e.g. passing wrong arguments), but to find the cause for an exception
it helps a lot if you can see local variables and especially parameter
values of all stackframes in Joda.
So the initial developer experience with Joda is much friendlier with
debug info contained.
If you create a deployment/installer of your app you can (and should)
strip debug info from all jars anyway.
Stephen Colebourne wrote:
Brian S O'Neill wrote:
I noticed that the classes in the Joda-time jar file contained full
debugging info. By default, javac only inserts line numbers and source
files. Local variable names are useful only to someone stepping
through the Joda-time code in a debugger.
I modified the ant javac task to only include line numbers and source
files, and the Joda-time jar file is now about 10% smaller.
Sounds good to me.
Stephen
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Joda-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/joda-interest
