Community
Participate
Working Groups
Created attachment 117964 [details] Test Case The generated code created does not reflect javadoc behavior. The first incorrect stub is generated when the following Extended String Literal is used: public static final String B = "Half" + " and " + "Half"; the stub file generated looks like this: public static final String B = "<extended string literal>"; And the HTML file created expresses the constant in the Constant Field Values as: public static final java.lang.String B "<extended string literal>" When I run the same class file through javadoc the Constant Field Values expreses it as: public static final java.lang.String B "Half and Half" The second incorrect stub generated is when you set a class variable using a Extended String Literal inside a method call: int C = D("Half" + " Complete"); the stub file generated looks like this: int C = D(ExtendedStringLiteral{Half Complete}); This is code is Syntacticly wrong and cause errors when javadoc is run on the stub file causing that file to not have an HTML file generated. I've Attached Files that will produce the discussed behavior.
Created attachment 117967 [details] Patch for ExtendedStringLiteral I split this one up into 2 patches since one changes the shadow code.
Created attachment 117968 [details] Patch for the AsmHierarchyBuilder This will adjust the AsmHierarchyBuilder to use the change made to ExtendStringLiteral properly.
all patches applied. See bug 257277 in case there is follow up work to be done... thanks for the patches! iplog