Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5543

include debug info in derby builds uploaded to maven

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.8.2.2
    • Fix Version/s: 10.15.1.3
    • Component/s: Build tools
    • Labels:
      None
    • Urgency:
      Urgent

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              rhillegas Richard N. Hillegas
              Reporter:
              sgbridges Sean Bridges
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: