[ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226739#comment-16226739 ]
Rick Hillegas commented on DERBY-5543: -------------------------------------- I have assigned this bug to myself. I think that line numbers by themselves (without the extra debug information) will only marginally increase the size of the Derby artifacts. The advocates for super-slim artifacts no longer actively contribute to Derby. I do not expect further resistance to this change. > include debug info in derby builds uploaded to maven > ---------------------------------------------------- > > Key: DERBY-5543 > URL: https://issues.apache.org/jira/browse/DERBY-5543 > Project: Derby > Issue Type: Improvement > Components: Build tools > Affects Versions: 10.8.2.2 > Reporter: Sean Bridges > Assignee: Rick Hillegas > Priority: Minor > > Looking at a strack trace from derby retrieved through maven, I see that > derby is compiled without debug information, this means line numbers are not > available in stack traces, > Caused by: java.lang.NullPointerException > at > org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.xact.Xact.openDroppedContainer(Unknown Source) > at > org.apache.derby.impl.store.raw.data.PageBasicOperation.findpage(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.PageBasicOperation.needsRedo(Unknown > Source) > and it is harder to debug code by setting breakpoints within derby. Derby > deployed to maven should have debug information included. > I'm not sure how this is controlled, but looking at pom.xml I see, > <!-- Specifies whether to package the sane (debug) or insane jar. > Valid values: sane|insane > --> > <sanity>insane</sanity> > The default should be sane. -- This message was sent by Atlassian JIRA (v6.4.14#64029)