Eclipse Autocomplete shows 'Problems During Content Assist' popups - java

Lately I've been getting these 2 strange error messages in Eclipse. These happen the first time i press . , such as in MyClass.myMethod(), pressing the . causes these messages to popup. They show up only the first time after Eclipse is started and don't show up again until next restart.
First error:
Second error:
These might be related to some new updates that I installed on Eclipse. Any ideas how to get rid of them?

Any Eclipse errors should be logged, so see if you can see them in the Error Log view. Open it either by pressing Ctrl+Shift+Q, L or using the menu Window > Show View > Error Log.
As Yuval A suggests, either find the existing bug (and read any workarounds) or report a new one in bugzilla - you'll be helping out Eclipse developers and users (not to mention yourself) by reporting the problem.

I get those as well from time to time. Bug in Eclipse, I believe.
Check out the content assist bug list. If nothing there is relevant to your specific situation you can open a bug.

Related

The cursor randomly disappears in Eclipse 2019-09 and sometimes stops writing

I have a very annoying problem with Eclipse 2019-09 (4.13.0) version: while I'm editing code (often when I copy and paste things or after accepting a code completion suggestion) the cursor (I'm talking about the text cursor: |) disappears completely! I cannot see it anymore, so I'm not able to detect on which part of the line I am! This is very annoying. I found a partial fix by installing the extension 'Vrapper': enabling and disabling it makes the cursor appear again.
Another problem I experience every time I press Ctrl+Space to ask for code completion suggestions, the cursor stops writing. After doing random things like switching tabs or opening new files the cursor starts to write again, but then the keyboard shortcuts stop working and I have to restart the entire IDE.
This behavior is intolerable, so I was wondering whether somebody else has had the same problem and how they have dealt with it.
The configuration of my system is:
OS: Debian, using i3wm+compton as a window manager on Xserver.
Thanks in advance.
Dead place, but I'm currently dealing with the same. The weird thing is that it happens on a per-file basis. Eclipse also treats that file as if it was not open, i.e. I can only save it through the 'Save all' method, not Ctrl-S ('Save') as I usually do. It's hellishly annoying, but it usually is fixed by reopening the file in question, and editing other files between the closing and reopening of other files.
If you have a better answer than this that you've found since, please, please post it here. It's annoying as all hell.
Minimize eclipse and maximize again.
Happened to me on Eclipse 2022-09 (4.25.0).

Generate comments in Reports for suppressed issues

I have a java project I'm assessing using Fortify. Some of the issues need to be suppressed and if so, a comment needs to be made describing why the issue is being suppressed.
How can I see this comment in the generated application report? I'm using the web interface, not workbench.
The suppressed issue appears, I just want to be able to see the comment along with it.
Thank you in advance.
EDIT:
I am able to work in the workbench if needed.
After awhile of searching I was able to figure out how to go about this.
For starters, I should mention that our Fortify scan was initiated by a Jenkins build. In the web interface, or SSC, I had to navigate to the artifacts tap. From there, I pressed the "Download Application File With Sources" button, which gave me an updated FPR that contained all of the suppressions and comments.
After that I had to use the Audit WorkBench to open that .fpr file. Then I chose not to override the default filter (not sure if that will pop up for everyone) and clicked the "Reports" tab.
I then selected the "Developer Workbook" template from the dropdown then clicked Issue Filter Settings. I checked "Suppressed" and deselected Collapse Issues (only Suppressed should be checked).
Next, I added a filter for only high's and criticals by selecting advanced to the right of filter and choosing "fortify priority order", "does not contain", "low" or "medium". There's an "||" to the top right you can click to have an additional filter.
Then I selected generate and it worked! The comments for suppressed issues will appear under "Audit Comments" in the report for each issue. Hope this helps others in the future.

Determining what perspectives/views are being loaded into workspace from Eclipse workspace.xmi

Eclipse Mars.1 RCP
I am trying to determine a way of knowing what views are being populated from the workspace.xmi upon re-opening of my program. In particular:
"org.eclipse.ui.console.ConsoleView".
My reason for this is the program I am working on uses a custom(somewhat?) console that is invoked by going into a "help" tab and clicking a "show console" button that executes a showConsole() function that opens the view and begins logging of errors or displaying stored errors.
The problem I'm having is that upon closing the workspace and re-opening it the view is created however the console shows "there is not console to display at this time" until you go back into the help tab and click show console which executes that logging function. I need a way of determining if that view is being created on startup so I can then start the logging automatically.
Has anyone ever done something like this before or know if it's possible without writing some huge parser to parse the .xmi looking for that plugin on startup?

How do I get a handle for the current workbench in eclipse?

I am developing my first plug-in for eclipse. My view works perfectly fine independently. The problem occurs when I try to get an instance of the view. When I searched online, I found that we can get the view by invoking Activator.getDefault().getWorkbench().getViewRegistry(). But Activator.getDefault() is returning null.
I have checked that in my plug-in's manifest file, the option 'Activate this plugin when one of the classes is loaded' is checked and 'Bundle-ActivationPolicy' is lazy.
Since I had no luck with 'Activator.getDefault()', I tried another approach: to get the workbench by calling PlatformUI.getWorkbench(). But I get the famous 'Workbench has not been activated yet' message. I thought I will have to wait till the workbench is created and so tried while(!PlatformUI.isWorkbenchRunning()){} but it never got past this loop.
Can someone please tell me what I am doing wrong?

Process Model Delta

I am using Eclipse IDE.
Sometimes, after I make some alterations to the code and try to run, I get "'Process Model Delta' has encountered a problem" error. If I try to run again, sometimes it runs (without giving any error again) or again gives the error and I have to restart Eclipse.
I am not pasting any piece of code here, because the code was perfectly fine in many situations when this error occurred.
Can anybody let me know the reason why this error occurs or what is the meaning of this error?
Thanks in advance!
I assume you're actually debug. It that's the case, the cause is in one of your breakpoints. See if it runs fine with breakpoints disabled. If that helps, try Debug view menu Java > Show System Threads.
Cheers,
Max

Categories