A note for the interested... was able to track down the problem into the
aspectj-maven-plugin. It uses the Maven project's dependencyMap for resolution
of the artefacts declared as AspectLib or WeaveDepenency.
Yeah... Maps can be dangerous at times :-P
If someone happens to be bitten by this issue, I've attached a patch here:
http://jira.codehaus.org/browse/MASPECTJ-87
Cheers,
Hermann
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
