It's all about the answers!

Ask a question

Code Coverage: Could not find corresponding java element


Kevin Kingsbury (611310) | asked Mar 06 '08, 2:16 p.m.
Hello.

I am setting up the code coverage feature of Jazz. I have it working in the build and the reports are reporting the code coverage in the build report. However, if I click on any of the classes/methods in the code coverage report, I get an error message "Could not find corresponding Java element".

Does anyone know what this means and how to fix it so it will not happen anymore? I have my entire source loaded into my eclipse workspace.

Thanks,
Kevin

2 answers



permanent link
Tobias Widmer (3211) | answered Mar 07 '08, 4:38 a.m.
kkingsbu schrieb:
Hello.

I am setting up the code coverage feature of Jazz. I have it working
in the build and the reports are reporting the code coverage in the
build report. However, if I click on any of the classes/methods in
the code coverage report, I get an error message "Could not
find corresponding Java element".

Does anyone know what this means and how to fix it so it will not
happen anymore? I have my entire source loaded into my eclipse
workspace.

Thanks,
Kevin


Hi Kevin

This message simply means that you don't have the corresponding code in
your local workspace. If you'd like to open the Java element from the
coverage report, you have to load the affected components first into
your Eclipse workspace.

HTH

Tobias
Jazz Coverage, Collaboration, Agile Planning team

permanent link
Kevin Kingsbury (611310) | answered Mar 07 '08, 10:46 a.m.
Hmm... The interesting thing is that I do have my entire project loaded into my eclipse workspace already. I went back and looked at the code coverage example that is in another thread and it looks like I am doing everything that is in that build file. I even added in the JDT compiler just in case that had something to do with it. But no go. I keep getting the same message.

Is there anything further that I can do to debug this?

Thanks,
Kevin

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.