Sample project has been created. See GitHub project <https://github.com/DavidWright916/aspectj_superclass_issue>
It occurred to me why my cflow attempt didn't resolve the issue. Cflow is evaluated at runtime, while the weaving happens at class load time for the mock instance. Anyway, the warnings still appear in the sample project, so happy cloning! -- View this message in context: http://aspectj.2085585.n4.nabble.com/error-can-t-determine-superclass-of-missing-type-tp4652184p4652186.html Sent from the AspectJ - users mailing list archive at Nabble.com. _______________________________________________ aspectj-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/aspectj-users
