[aspectj-users] Include / exclude when using aspect library in maven

Hi, I am currently moving aspects from a regular multi module maven project with production code to a separate aspect library (different maven artifact). However, I need different modules of my production code to use different subsets of the aspect library. Is there a possibility to limit

[aspectj-users] pointcut to match return statements

Hi, is there any way for me to match return null statements statically? I would like to create a policy enforcement aspect that forbids null returns unless the method is marked as @Nullable. I'm aware this check wouldn't be perfect because it could always be tricked with a variable: String

Re: [aspectj-users] pointcut to match return statements

On 06.01.2014 15:26, Alexander Kriegisch wrote: You can neither match return null nor assignments to local variables, only assignments to member variables. What you can do is match returning calls or executions and check their results dynamically like this: after() returning(Object

Re: [aspectj-users] pointcut to match return statements

On 06.01.2014 15:59, Alexander Kriegisch wrote: A) Returning null is not necessarily a programming error. Not handling null results gracefully might be though. I'm aware of that, that's why we allow the @Nullable annotation for such cases. B) How should it be possible to statically

[aspectj-users] APT and AspectJ in the same project, using Maven

by side. ;) I may be stupid, but I just can't find a way to do this. Can anybody help? Thank, Sean -- MostlyMagic.com - Sean Patrick Floyd IT-Consultant und Senior Java Developer Mobile: +49 170 4746496 Mail:mailto:i...@mostlymagic.com i...@mostlymagic.com Web: http