Community
Participate
Working Groups
Spawned from: https://bugs.eclipse.org/bugs/show_bug.cgi?id=426616#c4 Given this program: // -- import java.lang.annotation.*; import static java.lang.annotation.ElementType.*; @Retention(RetentionPolicy.RUNTIME) @Target(TYPE_USE) @interface Marker {} public class X extends @Marker Object {} this is what I see in the class file editor: / Compiled from X.java (version 1.8 : 52.0, super bit) public class X { // Method descriptor #6 ()V // Stack: 1, Locals: 1 public X(); 0 aload_0 [this] 1 invokespecial java.lang.Object() [8] 4 return Line numbers: [pc: 0, line: 6] Local variable table: [pc: 0, pc: 5] local: this index: 0 type: X }
Does this actually belong in JDT/Text ?
See org.eclipse.jdt.core.util.ClassFileBytesDisassembler.disassemble(byte[], String, int)
(In reply to Dani Megert from comment #2) > See org.eclipse.jdt.core.util.ClassFileBytesDisassembler.disassemble(byte[], > String, int) Thanks, this is the same thing we use that already works for us - so I suspected some customization issue at the abstraction use site. But it turns out we are inconsistent in our handling of SE8 annotations vis a vis SE7 annotations in DETAILED vs SYSTEM modes and all our tests use SYSTEM mode. This would require some work as there is too much detail we print today that would completely mess up the formatting, line breaks etc. Don't expect to get to this before 4.4.
Looking at my list of tasks for 4.4, I doubt that I'll get to this in 4.4 time. Retargetting to 4.5. If time permits, will pull back to 4.4
I don't expect to get to this anytime soon, any volunteers ?
I believe Shankha has worked on in this area. Assigning to him.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This issue still persists - keeping in the radar (may be 4.18 - until 4.18 target comes up - targeting 4.17)
Bulk move out of 4.19
