Bugzilla – Full Text Bug Listing
| Summary: | [Java discoverer] Could not retrieve interfaces : "AbortCompilation" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] MoDisco | Reporter: | Nicolas Bros <nicolas.bros> | ||||
| Component: | Technologies | Assignee: | Fabien Giquel <fabien.giquel> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | CC: | fabien.giquel, gdupe, hugo.bruneliere, modisco.web-inbox | ||||
| Version: | 0.9.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
MoDisco Java Discoverer uses jdt to parse and resolve all java classes. Just as jdt may log some errors at interactive compilation/navigation time, jdt may log such errors in error log when launched from MoDisco discovery. For instance I have already noticed some "XX cannot be resolved" error coming from jdt in error log when using MoDisco Java Discoverer. After that when opening the java editor on java file which has the problem, the "CTRL + CLICK" navigation also displays the "XX cannot be resolved" message. --> The problem is in the configuration of the projects which are analyzed. Jdt cannot do its job. Here, i think it is this kind of problem when I see in the stacktrace "IStyledLabelProvider cannot be resolved. It is indirectly referenced from required .class files". I close the issue. We may reopen it if you observe that the .class does not have the compile error "... referenced from required .class files" in your workspace. In such a case please describe the project test case. Bug not solved. |
Created attachment 193577 [details] stacktrace When benchmarking the Java discoverer on Eclipse projects (jdt, pde, jface, swt), I got a few dozen "Could not retrieve interfaces" error from JDT in the error log. See attached stacktrace.