I guess you mean the aspects are using intertype declarations. To support your basic use case, sounds like you can just keep everything in one project.
However, if you are building a reusable library and the initial target classes shouldn't be included, you will need to split the projects. However - intertype declarations create a strong coupling between the aspect and the target which can make this tricky to set up. What kinds of intertype are you doing? Are you intertyping onto an interface then using declare parents to apply that interface? Andy On 9 July 2010 06:59, <[email protected]> wrote: > I have a project, called MyAspects. It contains several aspects. It also > contains classes. Those classes need to use the public methods introduced by > those aspects. > > How do you setup the project to do this? Do I have to setup 2 projects and > keep my aspects in one project and everything else in another? > > The output should ideally be a library that clients use to potentially > introduce the aspects to their types as well as use the aspectj-enhanced > classes directly. > _______________________________________________ > 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
