- This topic has 7 replies, 3 voices, and was last updated 14 years, 3 months ago by
.
-
Posts
-
If I select Coverage As->Junit Test from the context menu in a Maven project, a dialog informs me that “No classes are selected for instrumentation”
In earlier versions, this did not need to be configured. If I open the dialog, the only classes available for instrumentation are those in my local maven repository; none of the project classes are present in the list.
What has changed?
stacey11,
We have not made any changes to MyEclipse specific to this issue.
Can you answer some questions for me?
1. Which version of Eclemma plugin you are working with ?
2. Can you check if this particular version is compatible with the corresponding Eclipse version (Eclipse 3.5)?
3. Do you see any specific errors in the .log file which is located at <workspace dir>/.metadata folder? If there are any, please paste them here for me.In earlier versions, this did not need to be configured.
Is it the same Eclemma version that is used in earlier version of ME and in the 8.6.1?
As installed by Pulse, eclemme is 1.5.1. Shouldn’t Pulse handle checking for version dependencies???
stacey11,
Pulse will not check for version compatibilities for the plugins.
Do you see any specific errors in the .log file which is located at <workspace dir>/.metadata folder?
If there are any, please paste them here for me.stacey11,
Can you do some steps for me?
1) Start Pulse explorer.
2) Select the profile and perform re-install and run. You might like to duplicate the profile( Select the profile->Right click context menu->Duplicate) before performing this step.
3) After the profile gets reinstalled, open the MyEclipse configuration center and install eclemma back.Let us know how it works for you.
Stacey,
I have provided some tests below. Can you please verify the same at your end.1) Please verify the preference settings with those on this link – http://www.eclemma.org/userdoc/preferences.html
2) Execute the project in normal run mode. If that doesn’t work then your app. might not execute in coverage mode either. In such case, you will have to create a proper launch configuration in Eclipse and then execute in the Coverage mode.
3) Open the coverage configuration dialog and delete all the coverage launch configurations. Then perform Junit test coverage from the project context menu. This should create a new launch configuration with default values. I assume this should fix the issue.
4) Also have you tried creating some dummy Java/Maven projects and execute coverage tests on them?
5) If the above steps don’t work, if possible please provide us the .classpath and .project files. You can email the same to support@genuitec.com ATTN Neeraj with the link to this thread.Hope this helps.
