- This topic has 22 replies, 14 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
Try a new project, does that work? If not, try a new workspace (File > Switch Workspace > C:\tempworkspace, hit OK) then a new project. Does that work?
Did you try restarting using the -clean command line argument? Stale plugin state can cause all sorts of problems.
We are building a .jar file with Ant. However, we cannot debug into this .jar after attaching the source code to the .jar. There are a couple of places on the web that say this can happen if building a .jar with Ant, but they give no solution. Does anyone know how to correct this (other than not using Ant)?
I just went to File => Export => JAR file and manually created the needed .jar file. I was then able to debug into the .jar after I attached the source and redeployed to the server. Seems Ant is the problem. Does anyone know why there is a problem with Ant building the .jar files?
The reason Ant is the problem is that by default the <javac> task does not include debug information in the generated class files. Just make sure to set debug to true and include all 3 of the debugging informaiton types. Please refer to the Ant documentation for the javac task for more information.
Thank you… rkalla..
That was the mistake. If have to change the javac option in my build.xml <javac debug=”true” … > and now after comiling i can install breakpoints.
Thanks again for your help… 🙂Georg
I run in a fairly complex environment where our build room built our project using java 50 however the runtime environement into which the project used a different build of java50 – an IBM specific thing I think called J9
When I launched my project for remote debugging with this j9 jvm, I got that unable to install break point error. I changed the way I launch this appliation to use the java 50 version it was built with and the error goes away.
Best Regards,
Greg
