[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233563#comment-16233563
]
Rick Hillegas commented on DERBY-5543:
--------------------------------------
When I compile the engine with these attributes set in the <javac> elements...
debug="true"
debuglevel="lines,source"
...then the size of derby.jar increases from 3.2M to 3.7M and line numbers
appear in stack traces. I will take these numbers to the developer community
and continue this discussion there.
> 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)
