Community
Participate
Working Groups
This option is now also used to report redundant type arguments specification with the diamond case. This should be updated in the help displayed for warning options as well as the batch compiler documentation.
Ayush, can you look into this in Olivier's absence ? Thanks.
Created attachment 200970 [details] proposed fix Updated the jdt.doc.user for the batch compiler option "unusedTypeArgs" and also added a new test in BatchCompilerTests to test this option. Also updated jdt.doc.isv project to add all new option APIs added for java 7 work - including redundant specification of type arguments and all the new formatter alignment and spacing options.
Satyam, could you please give this patch a once over ?
(In reply to comment #3) > Satyam, could you please give this patch a once over ? I meant you Jay - thanks.
Ayush, is there a reason why the message is different in the batch compiler documentation?
(In reply to comment #5) > Ayush, is there a reason why the message is different in the batch compiler > documentation? This is an oversight. I had shortened the message because it was exceeding the 80 character limit, but forgot to change that in the documentation. Thanks. Will correct it.
Created attachment 201059 [details] proposed fix v.1.1 Corrected above mistake
Changes look good. Just for the records, the patch includes documentation changes for the formatter options for try with resources and multi-catch as well.
Released in HEAD for 3.8M2 and in R_3_7_maintenance for 3.7.1
Verified for 3.7.1 RC2 using Build id: M20110824-0800
Actually, I am able to verify the text of the new warning message in the batch compiler. But if I look at F1 + batch compiler page, I don't see the new text "unused type arguments for method and constructor" but see only the old text "unused type arguments for method". Did I miss something ?
Created attachment 202148 [details] Proposed fix This is a doc change.
Released into the doc for next build 3.7.1.
Released as FIXED as the doc bundle has been updated.
Verified for 3.7.1 with build M20110831-1030. I still don't see the help documents updated with the change as observed in comment # 11. I suppose the documentation changes are not part of the M builds yet, are they?
Verified for 3.8M2 using build id I20110912-0800. (In reply to comment #15) > Verified for 3.7.1 with build M20110831-1030. > > I still don't see the help documents updated with the change as observed in > comment # 11. I suppose the documentation changes are not part of the M builds > yet, are they? Shows up properly with the M2 build.
