Eclipse debugger fails to start - eclipse

For the last few days, I have been getting the following error whenever I try to debug a project.
org/eclipse/jdt/internal/debug/core/model/JDIDebugTarget (wrong name: org/eclipse/jdt/internal/debug/core/model/JDIDebugTarget$AjcClosure1)
This problem occurs with every project in every workspace, even in a workspace I created after the problem started manifesting. Whether or not I have set any breakpoints, the problem still occurs.
I am using Spring Tool Suite 3.8.1, and I can still run projects, just not debug them.
Does anyone know what the problem may be?

I upgraded to version 3.8.4 of STS and I can now debug my projects. Something in my previous STS installation must have broken.

Related

Eclipse Java IDE restore

I was developing a plugin, using Eclipse IDE for java developers (Version: 2021-09 (4.21.0)
Build id: 20210910-1417)
During development, when I run it as an eclipse application, it opens a runtime-Eclipse application where the plug-in is present. In my setup this new runtime-eclips app opened from a folder next to the workspace, where C codes were present. (and my progrem would get the tests run in C , and get the results from it's exe)
Then I downloaded the Eclipse IDE for committers, which is a newer version. I downloaded it as a zip and after unpacking I run the eclipse.exe. My program had problems opening the runtime-Eclipse application in C there, so i went back to the older one which is installed on my computer.
After opening the original eclipse, on which I was working and had no problems, I was hoping everything will be fine. It opens the IDE for java developers (same version, same build) but I have the same problems with the runtime-eclipse application as the one I run as an eclipse.exe , (not recognising the C code?? I don't understand).
When i try to run the plug-in I get this error.
And when the runtime-app opens i get this error.
I cannot create C projects anymore on the runtime-app. I don't know the reason behind this.
Also I have billion of these
["java.net.UnknownHostException: downdload.eclipse.ort"]
[" org.eclipse.equinox.p2.core.ProvisionException: Unknown Host: http://downdload.eclipse.ort/eclipse/updates/4.2/content.xml "]
Thank you in advance!
I don't know if it is possible or not, since seemingly it did not update the older eclipse IDE. If it can be restored the way it was before i run the eclipse.exe, I would be happy.
eclipse.ort is obviously a typo, it should be eclipse.org, I don't know where it is coming from - but its possible you enter it yourself as update site
the runtime error means eclipse cannot resolve all dependencies, which means it could not load bunch of plugins including yours, you need to figure out why on your own, its not possible to debug this remotely, its best to start from the scratch in the new workspace
The solution was easier than expected. The run configuration was modified by the other eclipse version. It was not launched with every plugin. only a selected handful

Not able to debug in Eclipse

I came across this strange issue where I 'm not able to debug my application (Java Web Application) in Eclipse.
History:
I deleted and re-imported the same project again.
Debug was working before this.
I tried:
Refreshing my workspace (all the projects)
Did a Clean + Build.
Checked my debug configurations for valid port number inside eclipse.
Gave breakpoints on the obvious lines of code where I know the control will hit these points.
Update
I'm using JBoss server if that helps.
Any pointers which I might have missed out.?
Thanks!
Well, I've worked for years with Java web apps, using Eclipse and JBoss, and I've faced this issue multiple times.
What I'd usually do to fix this problem is erase .metadata folder from the workspace while Eclipse was closed (it will re-generate when opening again).

Eclipse Wizard does not close on "finish" in a production environment

I have an eclipse plugin which runs fine in the eclipse version i'm using for developing it. It basicly also runs fine if i export it and install it in a fresh keppler version.
My plugin contains a New Project wizard to create projects which can be used with the plugin.
Now if i used this wizard in my development eclipse if i click finish, everything runs fine the project is created and the dialog is closed.
If i do the same in the fresh keppler installation, the project will also be created and everthing seems to be correct but the dialog won't close until i hit cancel.
Now i really wanted to come up with more information but in the development environment there is no exception occuring.
Also when i start the fresh keppler one with the -debug option i won't get an exception if i hit finish().
Any ideas what could cause this problem or how i could get more information on this?
It is always worth looking in the .log file in the workspace .metadata directory when something unexplained happens to see if something has been logged.
In fact it is worth checking the log once in a while during plug-in development just in case something has been logged.

Eclipse Helios seems to be corrupted

I am working on an application in Eclipse Helios and since yesterday every change in the code is not being applied when running the application. I have no idea what is going on. Is my Eclipse corrupted? Have some of you faced such situation? Many thaks.
You have probably disabled the automatic build, so Eclipse never compiles your changes. Check the main menu Project -> Build automatically.

Can't run the sample project on spring STS

After installing STS successefuly on Juno, i opened a new MVC project, fixed the errors in the sample STS project by adding all the required spring jars, and now there are 2 problems:
I can't get the option: "Run on server" (altough i did set a tomcat's server in the workspace).
With every step i make (clean, delete etc') i'm getting the follwing error:
Errors occurred during the build.
Errors running builder 'Faceted Project Validation Builder' on project 'First_STS_Project'.
Could not initialize class org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
Errors running builder 'Validation' on project 'First_STS_Project'.
org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
This is not a local problem on my specific workspace, because i getting the same error in my second PC as well.
I don't recommend JUNO since it has many bugs and it also has a bad impact in performance. If you're in Windows, try to use short paths when installing the plugins or selecting the workspace. I have similar issues when working in windows. If I create a workspace in c:/users/Marcelo/Documents/java/workspaces, I always get issues, but whenever I change to "c:/workspaces" directly, works perfectly. Try with Eclipse Indigo instead. Also try to use the latest version of tomcat. If any of the previous recommendations fix the issue, (that could be weird), try to install the STS plugin again but check all the features, maybe a component is missing.