| [cdt-dev] Antw: Re: CODAN Traversing children by using method "processResource" | Invoke methode after checker work is done. |
|
Thanks for the reply.
I'll check the behavior again and eventually send a bug report.
Best regards
Kevin >>> Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx> 9/20/2011 7:10 >>> 1) I don't have API handy if you think method is not behaving as described in docs send bug 2) There is no such method now. The only way to do that write a checker that process whole structure (not each resource) and do the printing in that checker. Of you can always submit the feature request and path to implement such feature. On Tue, Sep 20, 2011 at 4:39 AM, Kevin Schon-contr <Kevin.Schon-contr@xxxxxxx> wrote: > Hello, > > please discard the first message. I forgot to add a subject. > > > i have two questions about the CODAN Framework, maybe someone could help me > with them. > > First question: > I implemented some checkers to check the file and folder sturcture of a > c-project against a given naming convention. > For this, I extended the class "AbstractCheckerWithProblemPreferences" and > used the method "processResource()". > Most of the time it's only necessary to check top level folders of the files > and folder structure, so it's needless to traverse any of the children. > But when i return "false" in the method "processResource()" the children > will still be traversed. > Do I have missed anything? > > Second question: > Is there a way to invoke a methode after a checker has done ist work? > For example, I'd like to check if there are files with the same name in > a c-project. So I have to store their names in a list or tree and after the > checker has traversed the last resource of the file and folder structure, > i'd like to compare these names. > Unfortunally I can't find any method, that is invoked at the end of this > procedure. > Does anybody know a way? > > Best regards > > Kevin > > P.S.: I'm using cdt-master 8.0.0 for this. > > > -------------------------------------------------------------------------------------------------------------------------- > > This message (including any attachments) contains confidential information > intended for a specific individual and purpose, and is protected by law. If > you are not the intended recipient, you should delete this message. Any > disclosure, copying, or distribution of this message, or the taking of any > action based on it, is strictly prohibited. > > Diese Nachricht (einschliesslich aller Anlagen) enthaelt vertrauliche > Informationen, die für einen bestimmten Empfaenger und Zweck beabsichtigt > und gesetzlich geschuetzt sind. Bitte loeschen Sie diese Nachricht, > falls Sie nicht der beabsichtigte Empfaenger sein sollten. Die > Veroeffentlichung, Vervielfaeltigung oder Verteilung dieser Nachricht sowie > die Vornahme von Handlungen aufgrund dieser Nachricht ist strengstens > untersagt > > _______________________________________________ > cdt-dev mailing list > cdt-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/cdt-dev > > _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev -------------------------------------------------------------------------------------------------------------------------- This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Diese Nachricht (einschliesslich aller Anlagen) enthaelt vertrauliche Informationen, die für einen bestimmten Empfaenger und Zweck beabsichtigt und gesetzlich geschuetzt sind. Bitte loeschen Sie diese Nachricht, falls Sie nicht der beabsichtigte Empfaenger sein sollten. Die Veroeffentlichung, Vervielfaeltigung oder Verteilung dieser Nachricht sowie die Vornahme von Handlungen aufgrund dieser Nachricht ist strengstens untersagt |