Re[2]: [ajdt-dev] Finding build errors in IProject programatically

[Dawid Pytel <pytel.dawid@xxxxxxxxx>]

Hi Andrew,

> I can't say exactly why this isn't working for you. I was just able to
> reproduce something similar on my end.
So I guess it could be a bug. I decided to give more details in bug
report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=266631
>   One thing that comes to mind
> is that are you sure the AJ build is actually occurring?  If there is
> a classpath error, the AJBuilder may stop before completing the build,
> whereas the JDT builder may be a little more robust.
I encounter a problem when I build project without classpath errors.

I get messages from compiler like:
AJC: error at private BadClassName test;

So the project is built and errors are found.

> If you can't get this working by looking at the project, another thing
> try would be to use a ResourceVisitor and ask each compilation unit
> directly for syntax errors.

> something like

>                 public boolean visit(IResource resource) {
>                         if (resource.getType() == IResource.FILE) {
>                                 // find markers
>                                 return false;
>                         }
>                         return true;
>                 }
Unfortunately, it still doesn't find any markers.

I hope the test cases will help. It would be great to automate a few
tests I must perform.

Thanks in advance.