|
|
|
Re: Populating "Problems" Tab [message #690037 is a reply to message #667651] |
Tue, 28 June 2011 20:42 |
Carl Knight Messages: 13 Registered: December 2010 |
Junior Member |
|
|
Our IDE has been using the DLTK 2.0. Because of some bugs in 2.0 that are fixed in 3.0 we have finally moved to the DLTK 3.0
In our DLTK 2.0 based IDE the problems tab is populated fine. In the new "experimental" DLTK 3.0 branch of the same, the problems tab is not getting populated - even though none of that code has changed.
Does anyone have a definitive fix or can tell me what we NOW have to do that we did not previously have to do to get this working again?
From my investigation here is what I can see:
1. The build context passed to my build participant has the errors set on it. i.e. It is getting populated.
2. The errors are reported for the unit. i.e. SourceModuleDocumentProvider.SourceModuleAnnotationModel reportProblems method is called. Everything seems fine there, and in the end the fireModelChanged() method is called.
Beyond that I'm not sure where I should be looking so if anyone knows, tell me.
Thanks.
- Carl.
[Updated on: Tue, 28 June 2011 21:30] Report message to a moderator
|
|
|
|
|
|
|
Re: Populating "Problems" Tab [message #694577 is a reply to message #690037] |
Fri, 08 July 2011 21:51 |
Timothy Wall Messages: 21 Registered: July 2009 |
Junior Member |
|
|
I've tracked down the SourceModuleAnnotationModel usage, and it appears to be creating ProblemAnnotations, but still nothing shows up in the problems view (still using dltk 2.0, since I haven't been able to get 3.0 to build/install on my eclipse 3.6 yet).
I have been using the problem reporter provided to the build participant's IBuildContext parameter. Is there something else that needs to be created/activated?
[Updated on: Sun, 10 July 2011 13:07] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04324 seconds