JEP 293: Guidelines for JDK Command-Line Tool Options - @-files

Alan Bateman Alan.Bateman at
Fri Oct 28 20:34:42 UTC 2016

On 28/10/2016 20:15, Robert Scholte wrote:
> :
> Now I'm getting new messages, often one of these:
> Error: module-info.class not found for hibernate.jpa module
> or
> Error: module-info.class not found for spring.context module
> or
> Error: module-info.class not found for spring.orm module
> So let's forget about the space, might be a corrupted file in my 
> repository, can't explain the exception though.
> Now I'm blocked by these errors. Yes, it is true that these modules 
> don't have a module-info.class, but that shouldn't be a problem, 
> right? Compiling the project with my module-info files went fine...
If there isn't a module-info.class in the root directory of these JAR 
files then they are considered to be automatic modules. Automatic 
modules can't be linked into a runtime image. I realize this isn't the 
main point of your thread but just mentioning it that you will always 
get an error from link when there is a dependency on an automatic module.


More information about the core-libs-dev mailing list