Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[aspectj-users] A multi-project oddiity: inter-type declaration conflicts with existing member

Here is my scenario:

Project A provides reusable aspect libraries and regular java classes woven with these aspect libraries.
Project B is the application that uses classes in project A.
In AJDT, I have project B depending on Project A and having it on the "AspectJ Aspect Path". 

One of my aspect libraries provides default implementations of interfaces. 

Everything works fine if I IDT the implementation on the interfaces as follows: (all in Project A)

interface IParent {    public void doit(); }
aspect Service { public IParent.doit() { // do it} }
class Child implements IParent;

I got this confliction error if I IDT the implementation on the child as follows: (all in Project A)

interface IParent  {  public void doit();}
class Child implements IParent  {  // }
aspect Service { public Child.doit() { // do it}};

The error is produced by compiling Project B which uses "Child", not by compiling Project A alone.

The 2nd implementation works fine if things are not splitted into multiple projects. 
So I suspect this is a bug.

Any insights?

Thanks a lot.

Charles

 



Back to the top