db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sitsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5543) include debug info in derby builds uploaded to maven
Date Wed, 15 Feb 2017 05:36:41 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867290#comment-15867290

David Sitsky commented on DERBY-5543:

Just chiming in here.. we have recently switched to Gradle and have also noticed the lack
of line numbering which is a real pain for diagnosing issues.  Can we please make the insane
version by default have line numbering?  The effect would be minimal and most Java projects
enable this by default.  Without this it makes reporting Derby issues less effective.. as
often the issues happen on customer sites and are not easy to reproduce (or even accessible).

> 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:
>            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
>         at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown
>         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
> 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

View raw message