I do not have experience with IAM and I am not sure what kind of AspectJ integration it comes with (if any). I am not sure how this product manages classpaths and if it knows how to add jars to the aspect/in path for compilation.
However, I do have experience with m2eclipse and AJDT. These two products are known to work together with little or no user configuration. If your pom.xml is set up correctly and you use m2eclipse (http://m2eclipse.sonatype.org/) to import the project into Eclipse, then AspectJ awareness will be enabled automatically if required. On Mon, May 17, 2010 at 6:36 AM, Chad La Joie <[email protected]> wrote: > Hi, completely new AJDT user here with, I think, a basic question. Does > anyone have any experience with using both Eclipse IAM (maven > integration) and AJDT? I am seeing some behavior that I did not expect, > which seems to be caused by the Maven and AspectJ project builders not > cooperating very well. > > I have a basic bean class to which I am trying to add annotations. For > example: > > public class Foo { > // fields, getters, setters > } > > public aspect FooJpaAspect { > public @type : some.package.for.Foo : @Entity > } > > When I run my unit test it's clear that the bean has not been annotated. > > My Env is: > Java 6 > Eclipse 3.5 > IAM: 0.11.0.201001181900 > AJDT: 2.0.2.e35x-20100105-0900 > > As I said, I'm brand new to using AJDT so I'm not even sure what > information to provide to help diagnose the issue. > > Any help would be appreciated. Thanks. > > -- > Chad La Joie > www.itumi.biz > trusted identities, delivered > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
