| Summary: | Support registering additional dependencies from compilation participants | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Andrew Clement <aclement> |
| Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 1.6.10 | ||
| Target Milestone: | 1.6.11 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Andrew Clement
proposed changes committed to AspectJ and to AJDT (e36). No tests for this yet though... Unfortunately, I don't think these changes will work. The first method to AjCompiler.addDependencies is a CompilationResult object, which AJDT does not have easy access to. Any possibility that you could rework the method so that it takes a java.io.File object instead? changed api to take a file. test also now added. It works but the dependency being recorded is still only obeyed when a structural change occurs - hope that is the meaning intended by the participant in question. |