Assuming that there *should* be something on you in/aspect path, this might be caused by a bug in the maven-eclpse-plugin in that it doesn't properly configure aspect paths on an eclipse project.
See bug 270554 for a way to specify in path and aspect path through maven. https://bugs.eclipse.org/bugs/show_bug.cgi?id=270554 Alternatively, you can use a plugin like m2eclipse that manages it for you. Let me know if this works for you. On Wed, May 13, 2009 at 11:51 AM, Wade Girard <[email protected]> wrote: > If it matters... > > When I open up the properties for the project, under the "AspectJ Build", > Inpath and Aspect Path are empty, and in the Output Jar tab the Output jar > is an empty field. > > AspectJ Compile does not have "Enable project specific settings enabled. > > > On May 12, 2009, at 9:57 PM, Andrew Eisenberg wrote: > >> On Tue, May 12, 2009 at 4:22 PM, Wade Girard <[email protected]> >> wrote: >>> >>> On May 12, 2009, at 5:28 PM, Andrew Eisenberg wrote: >>> >>>> How is the jar file being created in Eclipse? >>> >>> How should the jar file be created? I can take a peek at the settings. >> >> Well, there are many ways that it could be created: through ant, >> through pde, through eclipse exporting, and there may be others. >> >> I think you said that the compiled aspect class files do not appear in >> the jar that is created through Eclipse. This means that ajc is not >> being invoked and instead the jdt compiler (or javac) is being >> invoked. >> >> If you can tell me what mechanism is creating the jar, perhaps we can >> figure out why ajc is not being invoked. >> >> --a > > Wade Girard > [email protected] > > > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
