- 
    Bug 
- 
    Resolution: Fixed
- 
     P2 P2
- 
    9
- 
        b165
- 
        Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8178754 | 10 | Srikanth Adayapalam | P2 | Resolved | Fixed | b05 | 
                    Here is the quote from latest JLS 9: 
7.7. Module Declarations
"In the declaration of a module name (after module) and in any use of a module name (by requires, exports, or opens), every identifier in the name must end with a Java letter, or a compile-time error occurs. "
Compiler does not produce an error.
In cases when the last identifier ends with a digit compiler produces a warning.
Either the compiler should report an error or the spec should be less strict.
7.7. Module Declarations
"In the declaration of a module name (after module) and in any use of a module name (by requires, exports, or opens), every identifier in the name must end with a Java letter, or a compile-time error occurs. "
Compiler does not produce an error.
In cases when the last identifier ends with a digit compiler produces a warning.
Either the compiler should report an error or the spec should be less strict.
- backported by
- 
                    JDK-8178754 Javac does not enforce module name restrictions -           
- Resolved
 
-         
- relates to
- 
                    JDK-8177852 update javac handling of module names -           
- Closed
 
-         
- 
                    JDK-8176802 #VersionsInModuleNames issue -           
- Resolved
 
-