[ http://jira.codehaus.org/browse/MOJO-290?page=comments#action_63491 ]
Emanuel Bulic commented on MOJO-290: ------------------------------------ I've had relative success with setting up another lifecycle. You can completely customize the way your artifact is build, and replace the compiler with aspectj compiler. However, I just found a bug with the aspectj mojo; it can't resolve non-jar dependencies. > AspectJ mojos run in compile and test-compile phase, conflicting with > standard java compiler > -------------------------------------------------------------------------------------------- > > Key: MOJO-290 > URL: http://jira.codehaus.org/browse/MOJO-290 > Project: Mojo > Type: Bug > Components: aspectj > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Priority: Blocker > > > AspectJ mojos run in compile and test-compile phase, which mean that standard > java compiler may run before it, thus failing in some cases (I believe is > when a test class extends a main class already weaved). > Don't know if compiler can be removed from aspectj mojo or aspectj should be > moved to plexus compiler, if not it has to run in the process-sources and > process-test-sources phase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
