[jira] [Updated] (DERBY-5543) include debug info in derby builds uploaded to maven

["Rick Hillegas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-5543:
---------------------------------
    Attachment: derby-5543-01-ab-insaneWithLineNumbers.diff

Attaching derby-5543-01-ab-insaneWithLineNumbers.diff. This patch changes insane (production) builds to compile with just enough debug information to generate line numbers in stack traces. Tests run cleanly on sane and insane builds.


Touches the following files:

{noformat}
------------------------------

M       tools/ant/properties/sanefalse.properties
M       tools/ant/properties/sanetrue.properties

Add default values for ant's debuglevel compilation flag.

------------------------------

M       BUILDING.html

Added a description of the effect of the debuglevel compilation flag.

------------------------------

M       build.xml
M       java/build/org/apache/derbyBuild/build.xml
M       java/client/build.xml
M       java/demo/build.xml
M       java/demo/toursdb/build.xml
M       java/drda/org/apache/derby/drda/build.xml
M       java/drda/org/apache/derby/impl/drda/build.xml
M       java/engine/org/apache/derby/agg/build.xml
M       java/engine/org/apache/derby/authentication/build.xml
M       java/engine/org/apache/derby/catalog/build.xml
M       java/engine/org/apache/derby/database/build.xml
M       java/engine/org/apache/derby/diag/build.xml
M       java/engine/org/apache/derby/iapi/build.xml
M       java/engine/org/apache/derby/iapi/db/build.xml
M       java/engine/org/apache/derby/iapi/jdbc/build.xml
M       java/engine/org/apache/derby/iapi/reference/build.xml
M       java/engine/org/apache/derby/iapi/services/build.xml
M       java/engine/org/apache/derby/iapi/services/crypto/build.xml
M       java/engine/org/apache/derby/iapi/services/io/build.xml
M       java/engine/org/apache/derby/iapi/sql/build.xml
M       java/engine/org/apache/derby/iapi/store/build.xml
M       java/engine/org/apache/derby/iapi/types/build.xml
M       java/engine/org/apache/derby/iapi/util/build.xml
M       java/engine/org/apache/derby/impl/db/build.xml
M       java/engine/org/apache/derby/impl/io/build.xml
M       java/engine/org/apache/derby/impl/jdbc/build.xml
M       java/engine/org/apache/derby/impl/load/build.xml
M       java/engine/org/apache/derby/impl/services/build.xml
M       java/engine/org/apache/derby/impl/sql/build.xml
M       java/engine/org/apache/derby/impl/store/build.xml
M       java/engine/org/apache/derby/io/build.xml
M       java/engine/org/apache/derby/jdbc/build.xml
M       java/engine/org/apache/derby/mbeans/build.xml
M       java/engine/org/apache/derby/osgi/build.xml
M       java/engine/org/apache/derby/security/build.xml
M       java/engine/org/apache/derby/vti/build.xml
M       java/optional/build.xml
M       java/shared/build.xml
M       java/storeless/build.xml
M       java/tools/org/apache/derby/iapi/tools/build.xml
M       java/tools/org/apache/derby/impl/tools/build.xml
M       java/tools/org/apache/derby/tools/build.xml

Adjust build scripts to compile at the appropriate debuglevel.
{noformat}


> 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
>         Attachments: derby-5543-01-ab-insaneWithLineNumbers.diff
>
>
> 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)