JDK-8210674 : Need to add examples for use of javac properties introduced by Raw String Literals
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 12
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2018-09-12
  • Updated: 2018-09-19
  • Resolved: 2018-09-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 12
12 b12Fixed
Related Reports
Relates :  
JDK-8206981 - Compiler support for Raw String Literals
Relates :  
JDK-8210671 - CheckExamples.java fail after Raw String Literals checkin
Description
Need tests for

compiler.err.unicode.backtick
compiler.misc.feature.raw.string.literals
Comments
Strictly speaking, the missing files are not "tests" in any conventional sense of the word, since there are no assertions involved, other than a meta-check that there are examples for as many as possible of the resources in javac.properties and compiler.properties. The purpose of test/tools/javac/diags/examples is to provide simple examples of code which will cause diagnostics to be generated. This allows us to review the generated diagnostics in context, so that we can review (the quality of) the error message, as regards to its style and content. This is because it can be hard to discern style and content from the individual entries in the resource files, before they get composed for the user.
12-09-2018
Understood. Thank you.
12-09-2018