Unfortunately you can't use declare warning for that if you compile the warning at the same time as the aspect that does the declare @type.
If you had a two stage compile process you could do a first build with the declare warning and without the aspect doing declare @type - that would tell you if any of the code has it declared directly on the class. Andy 2009/12/23 Wim Deblauwe <[email protected]>: > Hi, > > In our codebase, we use the spring @ManagedResource annotation to expose > things via JMX. Sometimes, this is put on the class directly and sometimes > it is done via an aspect. Would it be possible to declare a warning when > this is done on the class directly. I would like to force that everything is > done via an aspect. > Is it possible to know that the @ManagedResource annotation was introduced > via an aspect? > > When do the declare warning statements happen? Is this after the declare > @type statements? Note that we are talking about 2 different aspects (1 > architectural aspect that enforces and 1 aspect per service that I want to > expose over JMX), so maybe the correct precedence might help? > > regards, > > Wim > > > > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
