[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] AJDT configurator for m2e
- From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
- Date: Tue, 3 Apr 2012 10:29:35 -0700
- Delivered-to: firstname.lastname@example.org
The outxml line causes the compiler to create the aop.xml file
automatically during the compile. This file is required for load-time
weaving so that the weaver knows where to find aspects at load time.
See more information here:
This file is not required for compile time weaving.
As for changing the way that the AJDT configurator works, that
wouldn't be a recommended way of doing things. When using m2eclipse,
classpath management of your project is delegated to m2eclipse. This
ensures, for example, that if you remove the aspectj maven plugin from
your pom, then your eclipse classpath is automatically updated to
reflect that. This wouldn't be possible unless m2eclipse had full
control over the classpath and delegated properly to configurators
(like the ajdt configurator) where appropriate.
On Tue, Apr 3, 2012 at 9:38 AM, multanis <nicolas.daniels@xxxxxxxxxxxxxx> wrote:
> I found this post because it was not working for le neither and it seems it
> doesn't work without:
> So I just wanted to know if this is mandatory, why and actually what it does
> Before using the configurator, I was simply adding this in my .classpath:
> <classpathentry kind="con"
> <attribute name="org.eclipse.jst.component.dependency"
> *<attribute name="org.eclipse.ajdt.aspectpath"
> It was working fine but of course was ovewritten each time a maven update
> project config was needed. Maybe the configurator should only write this
> line ?
> Thanks !
> View this message in context: http://aspectj.2085585.n4.nabble.com/AJDT-configurator-for-m2e-tp3862183p4529422.html
> Sent from the AspectJ - users mailing list archive at Nabble.com.
> aspectj-users mailing list