Watter wrote:
>
> I'm trying to use the aspectj-maven-plugin but I'm hitting some odd
> issues. Here is how the plugin is configured:
> .....
>
> I notice that the maven process isn't attempting to run the normal
> "compile" goal until after the aspectj compilation goal. Is that what it's
> supposed to be doing? Is the reason aspectj can't see any of the other
> classes in my project because they haven't been compiled yet? Why would it
> run int hat order then?
>
> For what it's worth, if I do the load time weaving (using a
> META-INF/aop.xml config that's functionally identical to how I have the
> plugin configured in maven) , then everything works fine.
>
> Any idea what might be going on?
>
Never mind. Since I had more experience with the load time weaving, I
assumed the compile time weaving worked in a similar manner with respect to
what files needed to be specified. With the load time, I just told it to
weave the one file that I had marked with the Spring annotation,
@Configurable. With the compile time weaving it actually needs to normally
compile the class and therefore need access to a large portion of the java
files in my project.
Unfortunately, the spring-aspects.jar file contains not only the aspect
associated with @Configurable, but also one related to transactions that
conflicts with the normal @Transactional management of my database access.
Anyway, now that I know the root of the problem, I think I can figure it out
a solution.
--
View this message in context:
http://www.nabble.com/aspectj-plugin-not-weaving-tf4107688.html#a11690154
Sent from the mojo - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
