Summary: | Utility.java:1024 from BcelWorld.java:155 org.apache.bcel.classfile.ClassFormatException: Invalid method signature: <missing> | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Frederic Bages <frederic.bages> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 1.5.0M3 | ||
Target Milestone: | 1.5.0 M4 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Frederic Bages
2004-10-15 10:07:16 EDT
In fact it seems that it's when i uncomment the following part of the aspect : Object around() : myClass() { long start = System.currentTimeMillis(); try { return proceed(); } finally { long end = System.currentTimeMillis(); //recordTime(start, end, thisJoinPointStaticPart.getSignature()); } } Even with the dependency added the problem is still present. I use this aspect in another project but not to wave libraries. OK, there were some other libraries that were missing. My understanding of the problem is that if we try to wave libraries that have dependencies whitout adding these dependencies to Maven project.xml that crash the compiler. Now that i've added all the dependencies the aspect is being compiled correctly. Hi. I hope to get to this bug soon (early next week?) - you shouldn't be able to make the compiler crash. Is there any way you can keep around the setup you have that causes it to appear so I can try and fix it and let you see if my fix works? (I imagine I'll have trouble trying to recreate it here). let me know, thanks, Andy. I've made a backup to be able to test your patch if needed. It seems (not sure) to appear when weaving a webservice client library made with JSWDP 1.4 (JAX-RPC) ... I'am on holiday next week so i won't be able to check my mail until October 25. Have a nice WE. I'll do something about this before 1.5.0M3 ! not sure where Andy got to on this, but we shouldn't lose sight of it in the run-up to M4 This is the same issue as bug 73504, for which I committed a fix this morning. The compiler is now much more tolerant of missing types (and the <missing> signature scenario should not be possible any more). Fix will be available in next published AspectJ dev build (later on today). *** This bug has been marked as a duplicate of 73504 *** |