You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joshua White (JIRA)" <ji...@codehaus.org> on 2006/03/25 01:06:11 UTC
[jira] Commented: (MPASPECTJ-6) autoweave test code before running
tests
[ http://jira.codehaus.org/browse/MPASPECTJ-6?page=comments#action_61921 ]
Joshua White commented on MPASPECTJ-6:
--------------------------------------
As of version 3.2, it seems that this fix has reversed itself. No matter where I put my aspect as a pregoal, it always seems to use the value of "maven.compile.src.set" for the value of "maven.test.compile.src.set". I am assuming that this is because it doesn't have access to the test plugin as referenced above.
> autoweave test code before running tests
> ----------------------------------------
>
> Key: MPASPECTJ-6
> URL: http://jira.codehaus.org/browse/MPASPECTJ-6
> Project: maven-aspectj-plugin
> Type: Improvement
> Environment: maven-1.0-rc1, WinXP, J2SE 1.4.2
> Reporter: John Fallows
> Fix For: 3.1
> Attachments: aspectj-test.txt
>
>
> I have recently started to use virtual mock objects (http://www.virtualmock.org) that make heavy use of AspectJ in the test cases of a maven project.
> I noticed that the latest AspectJ plugin has support for autoweaving the project sources, but not the test sources.
> Once you have resolved how to weave the compiled classes instead of just the JAR, how difficult would it be to autoweave the test classes as well?
--
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