• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 287
  • Last Modified:

Ant compiled program not showing source code line in errors

When i compile my program and build the jar package using ant, and then execute that jar package and hit an error, the displayed java error doesnt seem to know about the source code.  It prints out the stack trace, but doesnt include any line numbers so i dont really know where the error was. When i run the same code in my IDE, JBuilder, and hit an error, it always tells me where in the source code the error was. Here is my build.xml file for my package. Any suggestions on what to change so it can reference the source code line number when errors occur?

<?xml version="1.0"?>
<project default="dist" name="Project Eric">
     <description>Stat Program</description>

    <property name="srcDir" location="/usr/local/jakarta/webapps/NBNFBA/WEB-INF/src"/>
    <property name="buildDir" location="build"/>
    <property name="distDir" location="dist"/>
    <property name="tomcat.lib.dir" value="/usr/local/jakarta/common/lib"/>
    <property name="mysql.lib.dir" value="/Library/Java/Extensions"/>

    <path id="java.libs">
      <fileset dir="${tomcat.lib.dir}" includes="servlet-api.jar"/>
      <fileset dir="${tomcat.lib.dir}" includes="mail.jar"/>
      <fileset dir="${tomcat.lib.dir}" includes="activation.jar"/>
      <fileset dir="${mysql.lib.dir}" includes="mysql-connector-java-3.0.10-stable-bin.jar"/>

    <target name="init">
       <mkdir dir="${buildDir}"/>
       <mkdir dir="${distDir}"/>

    <target name="compile" depends="init">
       <javac srcdir="${srcDir}" destdir="${buildDir}" classpathref="java.libs"/>

    <target name="dist" depends="compile">
       <jar destfile="${distDir}/package-${DSTAMP}.jar" basedir="${buildDir}">
           <attribute name="Built-By" value="${user.name}"/>
           <attribute name="Main-Class" value="fantasy.gui.Main"/>
           <attribute name="Class-Path" value="mail.jar activation.jar servlet-api.jar mysql-connector-java-3.0.10-stable-bin.jar "/>
       <jar destfile="${distDir}/package-src-${DSTAMP}.jar" basedir="${srcDir}"/>

    <target name="clean">
      <delete dir="${buildDir}"/>
      <delete dir="${distDir}"/>

1 Solution
In your compile task use:

<javac srcdir="${srcDir}" destdir="${buildDir}" classpathref="java.libs" debug="on"/>

I think this works to give you better line info
check the dir where the source code is. Maybe it is unreachable.
HokesterAuthor Commented:
i know the source code is reachable because the compile works and the package is successfully built.  ill give the debug try an attempt tonight when i get home.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Good luck.
u can try like this

 <javac srcdir="../com/xxx/xxx/xxx/dao" destdir="${build.jar}/classes"
                    debug="true" debuglevel="lines,vars,source"/>  

this will show you the line number when u use the classes anywhere.

HokesterAuthor Commented:
this worked exactly like i wanted it to. Now that i knew the command i found all kinds of information about what you said in the ant documentation.  kiranhk, i gave the points to gdrnec because you mostly said the same thing, he just beat you to it.  It is worth noting that if anyone reads this in the future that i had to delete my build directory because the files needed rebuilt using this debug on feature. When i originally tried the solution it did not work. I deleted the build directory, so that everything had to be rebuilt, and then it worked just like i wanted.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now