#297 Debugging information still missing from maven artifacts

open
5
2013-11-26
2013-10-30
Adar Dembo
No

I looked at https://sourceforge.net/tracker/index.php?func=detail&aid=1960355&group_id=23316&atid=378134 before filing this bug.

The class files in the 2.3.1 maven artifact appear to be missing all debugging information, making debugging that much more challenging. The aforementioned bug report mentioned a separate jar for debug info but I can't find it. I did find an older hsqldb-j5 jar, but it too is missing debugging information.

Discussion

  • Adar Dembo

    Adar Dembo - 2013-10-30

    Ahh, I was expecting the debug artifact to be named differently from the regular hsqldb artifact.

     
  • Fred Toussi

    Fred Toussi - 2013-10-30

    It is named differently:

    hsqldb-2.3.1-jdk6debug.jar

     
  • Adar Dembo

    Adar Dembo - 2013-10-30

    Any chance you would be willing to add debug information to the default artifact? http://stackoverflow.com/questions/1872491/why-are-some-java-libraries-compiled-without-debugging-information suggests that it shouldn't add overhead.

    I'm asking because even though I can use a <classifier/> tag to tell maven about the -jdk6debug artifact, I can't find a way to customize maven-eclipse-plugin so that it'll look for -sources and -javadoc for the sources/javadoc artifacts. As-is it's looking for artifacts with names like -jdk6debug-sources and -jd6debug-javadoc.

     
  • Fred Toussi

    Fred Toussi - 2013-11-26
    • assigned_to: nobody --> unsaved
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks