Summary: | invalid aspectj path throws filenotfoundexception | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Frank Stolle <frank> |
Component: | Compiler | Assignee: | Andrew Clement <aclement> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | DEVELOPMENT | ||
Target Milestone: | 1.5.1 | ||
Hardware: | Macintosh | ||
OS: | Mac OS X - Carbon (unsup.) | ||
Whiteboard: |
Description
Frank Stolle
2005-12-19 06:28:40 EST
This seems to be ok on the command line - you get a message saying "Bad aspectpath ...". In the AJDT environment we'd like the compiler to return a compile problem rather than throw an exception. command line verification is done in BuildArgParser. AJDT takes a different route into the weaver. I've changed AjBuildManager to report a problem for entries on the aspectpath that don't exist. I also upgraded the AJDT-like test harness we had to allow setting of an aspectpath for a project. fix checked in, waiting on build. fix available. |