Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Re: [aspectj-users] Crosscutting model sanity check

It does stop once the view is closed.  However, you are right in that
there should be a way to disable it if you don't want to see it.

It would also be nice to see the actual amount of time spent on the
model checking, but that is hard to calculate since the penalty occurs
throughout the compilation as messages are produced.

Can you raise an enahncement request for this?

On Fri, Mar 13, 2009 at 8:13 AM, Thomas M. Hofmann
<email@xxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> I read about that too but I would like to be able to see the trace without the performance panelty to be able to compare times with 1.6.3.
>
> Also I am not sure if the model checking stopsonce I close the ADJT again.
>
> Thomas
>
> ----- Ursprüngliche Nachricht -----
> Von: Andy Clement <andrew.clement@xxxxxxxxx>
> Gesendet: Freitag, 13. März 2009 16:08
> An: aspectj-users@xxxxxxxxxxx <aspectj-users@xxxxxxxxxxx>
> Betreff: Re: [aspectj-users] Crosscutting model sanity check
>
> Hi Thomas,
>
> I'm sure Andrew will comment shortly but I'm under the impression that the
> checking is only done if you have the AJDT Event Trace view open.  We have a
> few diagnostics like that - where you pay no cost for them if that view is
> closed.
>
> Andy.
>
> 2009/3/13 Thomas M. Hofmann <email@xxxxxxxxxxxxxxxxx>
>
>> Hi,
>>
>> can the crosscutting model sanity check be turned of in 1.6.4 dev build
>> somehow? I would like to see how much time is spent on it since
>> incremental compilation was way faster in 1.6.3.
>>
>> Thanks,
>>
>> Thomas
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>


Back to the top