EclEmma not working - eclipse

I'm trying to use EclEmma with Eclipse, but I can't get it to work. I can't see the button that's supposed to launch my project in Coverage mode, There;s also no such option in Run menu:
I've tried to fix it in two ways I've found on the Internet, and none worked:
the EclEmma help page says that I should enable the Coverage command group on the Commands tab in the Customize Perspective dialog, but there's no such tab in the dialog and no Coverage command group in existing tabs
I tried to find “Java Code Coverage” in Window > Preferences > General > Appearance > Label Decorators menu - not there
I'm using Eclipse Mars.2 Release (4.5.2) on Windows 10, I have EclEmma v. 2.3.3.201602231923 (according to Help > About Eclipse > Installation Details) installed via Eclipse Marketplace. I have no idea how to fix it, I'll appreciate any help.

In eclipse 4.9 (2018-9) the option to enable the "Coverage as ..." command can be found in "Customizing Perspective" (rightclick on the perspective shortcut), then on tab page "Action Set Availability": Click the "Java Code Coverage" option.
Another problem I encountered: Although the "Coverage as..." command was available, there was no result visible at the end in the view "Coverage". The problem can be solved by following the advice from the eclEmma FAQ:
The Coverage view stays empty and there is no source highlighting. Why?
In Eclipse preferences there is an option Launch in debug mode when workspace contains breakpoints under Run/Debug → Launching. If this option is enabled and there are breakpoints in your workspace coverage mode will not work, because it is automatically replaced with debug mode. Set this option to Never if you want to run code coverage analysis.
BTW: I am using eclEmma plugin 3.1.2

Related

Right-click menu not showing in Selenium IDE

On this Selenium documentation page, it says "You can export either a test or suite of tests to WebDriver code by right-clicking on a test or a suite...", but when I right-click, I just get the web browser's right-click menu instead of Selenium-IDE's menu:
I have found that quitting Firefox and starting it again will give me the proper right-click menu, but wondered what I was doing to cause it, and if the developers know about this.
Firefox 71.0 (64-bit) on Windows 7
Selenuim IDE Version 3.16.1
This is because you are trying to export test from different tabs. 'Executing' tab is opened on your screen, but 'Tests' tab is opened on documentation screenshot .
About restarting Selenium IDE: 'Tests' tab opens as a main window after restart, so exporting is available there. When you start running tests in Selenium IDE 'Executing' tab automatically opens and exporting is not available. You should change tab by clicking on the tingle near tab name and select 'Tests' tab where you can export your test.
If you think that this is not correct behavior you should create issue here

Eclipse Oxygen with pydev has wrong index, cannot rebuild it

I have installed pydev on eclipse oxygen, and globally search the content by pressing "Ctrl+H", but the search result has wrong line numbers, I cannot get correct search result either by doing "Refresh" or re-creating the workspace, anyone has come into the same situation and help me ? Thx.
Do you have auto-build turned on (in the menu: project > build automatically)?
You can also trigger a reindex by doing the following: open a PyDev editor, trigger: Ctrl+2 and then choose --reindex in the menu that opens (considering you're doing a search in the PyDev tab).

How to see what triggered "Build workspace" in Eclipse

My eclipse is constantly running "Build Workspace" tasks. It is not a long running builds, more like 1 build a second.
Sometimes I'd see 10 "Build workspace" tasks sleeping and waiting in the Progress tab.
I'd like to know what is triggering those builds. I have many plugins installed.
What is the way to troubleshoot this?
Here are some steps to help you debug what is going on.
Download the Eclipse Classic SDK for whatever version of Eclipse you are currently using. For Juno that link is here.
Open the eclipse.ini for your current normal eclipse and add the following options: -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
Start your Eclipse instance that you want to debug, it should pause at the splash screen
Unzip the Eclipse classic SDK and start that Eclipse instance
Open the Plugins view
Find org.eclipse.core.resources
Right click and select "Add to Java Search"
Open Type dialog, type in "BuildManager"
You should see a class from that plugin be given as an option, then open it
Find the line that looks like: prereqs = currentBuilder.build(trigger, args, monitor); It should be about line 728 (For Eclipse Juno)
Set a breakpoint here
Create a new Remote Java Application debug configuration and point to localhost port 8000
Launch this debug configuration
You should see your other Eclipse instance startup
Now every time the Eclipse build manager fires off a build (which should happen on all of those Build Workspace jobs), then you will see this breakpoint be hit and you can find out what builder is firing.
Update 1
If you need source to other Eclipse bundles they can also be added in the "Plug-ins" view. Select all the plugins there and right-click and use Add to Java Search
What plugins do you have installed that are currently active?
Press CTRL+3 type "plugin" and then choose plugin registry.
In the plugin view right click and choose "Active Only"
Check the non-essential core plugins (for example related to servers which automatically build & publish)
Post a screenshot of active plugins if you need any more help
You may have build automatically checked which will build when you save. Check under the nav Project > Build Automatically
Other way to close all unused projects.
Further, for good view, use filtering: View Menu -> filters -> Check 'Closed Project'.
Sometimes if you have > 20 opened projects you can observe constant 'build workspace' tendency.

Eclipse error: No source available for ""

Using Eclipse Helios in Mac OS X Leopard and debugging C++ code calling fsf gdb 7.1, the debugging stops at first line of main. Then after the first step I get
No source available for ""
View disassembly
Why this error? Should I give additional options for compilation? Eclipse generated automatically the Makefile
I had the same problem and the following solved it:
Go to menu Run->Debug Configurations... and a dialogue window opens. On the left there should be selected your project name (say MyProject for example) under C/C++ Application. If not select it. Then on the right side, select the tab main and make sure that in the textbox under C/C++ Application reads: Debug/MyProject. Also check that Debug is selected in the dropdown box next to Build Configuration: below.
In my case instead of Debug/MyProject, it was Release/MyProject. I never understood why. Anyway...
Hope that helps

How to change active launch configuration in Eclipse CDT

Feeling rather dumb: I have a C++ project, using Eclipse CDT (Eclipse 3.6, CDT 1.3.1).
I have defined more than one launch configuration: each points to a different executable within the project. But, when I press F11 to debug, Eclipse always loads the first configuration, and I can find no way to make it launch the 2nd one instead.
Surely this deserves a menu or dialog setting somewhere?
For each of your projects:
Project > Properties > C/C++ Build > Manage Configurations... > Set Active