[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [Dltk-dev] Error reporting API
|
What's the best place to look to identify the most significant changes between DLTK 2.0 and 3.0? If the only answer is "look at the code", then could you at least provide a synopsis of the tags available in the code repository?
I've been referring to the CVS MAINTENANCE_2.0 tag so far.
On Jun 20, 2011, at 4:15 AM, Alexey Panchenko wrote:
> Hi Robert,
>
>> i'm currently using the following code to report syntax errors in my plugin
>> to the DLTK-engine:
>>
>> IProblemSeverity severity = ProblemSeverity.ERROR;
>>
>> IProblem problem = new DefaultProblem(filename, message,
>> IProblem.Syntax,
>> new String[0], severity, offset, offsetend, line);
>>
>> // IProblemreporter instance
>> reporter.reportProblem(problem);
>>
>>
>> The error shows up in the editor, but i get a deprecation warning for the
>> DefaultProblem constructor.
>
> it expects you to define your own identifier instead of IProblem.Syntax
>
>> This works in Eclipse 3.7, but in 3.6 i'm getting a NoClassDefFoundException
>> for
>>
>> org.eclipse.dltk.compiler.problem.ProblemSeverity.
>>
>>
>> Is there a recommended way of doing this - possibly with
>> backwardscompatibility to the 3.6 API ?
>
> Install DLTK 3.0 into Eclipse 3.6.
> Unfortunately there are some incompatibilities in DLTK 2.0 (released
> with eclipse 3.6) and DLTK 3.0 (released with eclipse 3.7)
>
> Regards,
> Alex
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
