So a couple weeks ago my Eclipse IDE no longer allowed me to remotely debug my application saying that it was unable to install breakpoints because line numbers were not be
This error might also be generated if your Eclipse workspace simply has some invalid (stale or corrupted) breakpoints set. In the Breakpoints view, look for breakpoints that might be set in classes that were moved or deleted, and delete them.
The error can be caused by the source code you have in Eclipse not matching the code used to build the application you are remotely debugging. Try rebuilding and rerunning the app and refreshing the source in Eclipse.
In order to re enable the message : Preferences => java => debug . it is at the bottom of the screen : "Warn when unable to install breakpoint du to missing line number attributes"
For the problem about installing breakpoints, try to add a -g to your javac command line in ant (debug attribute of you compilation task, http://ant.apache.org/manual/Tasks/javac.html)
Eventually check if you have not mapped your project on a JRE instead of a JDK in eclipse.
I think you may want to try adding -g to the compilearg in your ant build.
<javac sourcepath="" srcdir="${src}" destdir="${build}"
classpath="xyz.jar" debug="on">
<compilerarg value="-g"/>
</javac>
Also if you are unsure if break points are working just put a break point in an early point in your code that you know is getting executed. you can also add a print statement to ensure that the break point is being passed by.
I ran into the same problem and @jondissed and @twister answers didnt help and I'm not using a custom ant task so I tried:
What finally worked for me was
Debug now halts at breakpoint.
Update 1 - apparently Eclipse just gets angry at times as I just fought with it for about 10 minutes when the above appeared to not be working and while it popped the error, I closed it and it still stopped at the new, single breakpoint :-/
Update 2 - ran into the issue again, Eclipse is just being pissy about it and even update 1 doesn't fix it - it's also affecting modified code not being deployed so when Eclipse gets in it's "mood", a clean and build then full deploy of the project works O_o