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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
