Summary: | Incremental compilation does not build using reweavable | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | David Knibb <dknibb> |
Component: | Compiler | Assignee: | Andrew Clement <aclement> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | 1.5.0RC1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
David Knibb
2005-09-08 06:44:57 EDT
andy will try to reproduce this... I dont think this can go wrong anymore .... Xreweavable is the default now and users are LTWing ... but I'll try to recreate. I cant get this to fail as described - I think making reweavable default and improvements to LTW have resolved it. I tried: Create project P1, an AspectJ project. In it, I have a class and an aspect that affects this class. It compiles and runs fine. Create project P2, an AspectJ project. In it, I have an aspect that would affect the class in P1 if it was woven with it. I then create a LTW profile for project P1 that has P2 on its aspectpath - when this runs we fail. The error is that the aspect from P1 isnt 'declared' and so the class in P1 can't be rewoven - this is a sensible error and may well be what David was encountering but previously we just failed in a horrid way rather than like this. I then added P1 to the aspectpath so that the aspect from P1 can be found at LTW time - we then run successfully with both aspects affecting the class. magic! I'll close this, we can reopen if someone else hits it... |