title: How to prevent proguard from removing "module-info.class" from the output jar?
body: <p>I'm upgrading a Java desktop application to JDK10 and need to leverage modules to use the <code>javapackager</code> to build a native package.</p>
  <p>Everything was working great until I added an obfuscation step using Proguard (6.0.2).
  Once I enabled obfuscation (using a working proguard configuration file from the &lt; JDK9 project) it works as expected but Proguard removes the <code>module-info.class</code> from the output JAR which prevents <code>javapackager</code> from finding the module.</p>
  <p>According to Proguard's documentation for the <code>injars</code> parameter</p>
  <blockquote>
  <p>By default, any non-class files will be copied without changes.</p>
  </blockquote>
  <p>The problem here is that <code>module-info.class</code> is a &quot;class&quot; file (albeit a weird one). The &quot;keep&quot; rules depend on class names so I don't think there is any rule I can use to prevent this removal.</p>
  <p>How can I get Proguard to keep the <code>module-info.class</code> file?</p>