Re: [ajdt-dev] Problem with Project dependency / Aspect Path in Eclipse

["prg@xxxxxxxxxxxxxxx" <prg@xxxxxxxxxxxxxxx>]

    prg@xxxxxxxxxxxxxxx schrieb:
    > just hit a strange behaviour;
    ...
    > about to reorganise a huge (AspectJ) project in Eclipse, to split
    > it into a series of dependent projects. Now, the very basic set 
    > "Commons" contains some Aspects, which need to be applied to the 
    > other parts.
    
    > Anyhow, building the dependent Project "Part-1" causes the message 
    > "The project was not built since it depends on Part-1,
    > which has build path errors".
    
    > Andrew Eisenberg wrote:
    >> There's nothing out of the ordinary that I can see in your project 
    >> files.  In order to narrow down and see if AJDT is the problem, can
    >> you try removing the AJ nature from both projects and see if the
    >> build path problem goes away?
    
    >> If it does, then can you add the natures back, and then just remove
    >> commons from the classpath of Part-1? If the problem goes away 
    >> under either of these circumstances, I'll raise a bug and try to 
    >> get a dev build out there that will provide some better 
    >> diagnostics.
    
    See https://bugs.eclipse.org/bugs/show_bug.cgi?id=288395
    
    
    Andrew, many thanks for resolving this issue,
    which has bitten us quite badly!
    
    I'm writing this short note, as the Problem might be of general
    interest. As it turned out, the root cause where some spurious
    Entries in the *Manifiest* hidden within some of the dozens of
    library Jars in our project's dependencies: Some of them declared
    an "Classpath" setting, which of course no one ever notices or
    cares about ;-)
    
    
    Cheers,
    Hermann Vosseler