Summary: | The compiler crashes when using aspect libraries created without using -noweave | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Ramnivas Laddad <ramnivas> |
Component: | Compiler | Assignee: | Jim Hugunin <jim-aj> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Ramnivas Laddad
2003-04-10 04:08:55 EDT
This is correct compiler behavior, but absolutely horrible error handling. This is being listed as a P3 bug but will hopefully be fixed for 1.1 anyway. You should only be able to pass files compiled with -noweave as an input to - injars. This test is only enforced for code that contains aspects or was actually woven into. The expected model is to provide aspect libraries using the -aspectpath option. This way you can ensure that the aspect library code will not be modified by any weaving process and the same binary library can be used for weaving with multiple targets. I'd recommend a process such as: ajc -outjar tracing.jar TraceAspect.java ajc -aspectpath tracing.jar Test.java fixed in tree, and test in new/options11 This now produces a nice error message instead of an exception. |