"Command execution failed" when packaging

[DBChoco]

I'm submitting a…

• [x] bug report
• [ ] feature request
• [ ] other

Short description of the issue: When I try to package my app on Linux, I get this message

[ERROR] Failed to execute goal io.github.fvarrui:javapackager:1.6.6:package (default) on project Salawat: Command execution failed: /usr/lib/jvm/java-18-openjdk/bin/jdeps -q --multi-release 18 --ignore-missing-deps --print-module-deps [Ljava.lang.String;@aca3c85 /home/smuky/IdeaProjects/salawat/target/salawat/libs/*.jar /home/smuky/IdeaProjects/salawat/target/salawat-1.0-runnable.jar -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Steps to reproduce the issue: Here is the plugin section of my pom.xml:

<plugin>
  <groupId>io.github.fvarrui</groupId>
  <artifactId>javapackager</artifactId>
  <version>1.6.6</version>
  <executions>
      <execution>
          <phase>package</phase>
          <goals>
              <goal>package</goal>
          </goals>
          <configuration>
              <!-- mandatory -->
              <mainClass>io.github.dbchoco.Salawat.Main</mainClass>
              <!-- optional -->
              <bundleJre>true</bundleJre>
              <generateInstaller>true</generateInstaller>
              <administratorRequired>false</administratorRequired>
              <createTarball>true</createTarball>
              <platform>auto</platform>
          </configuration>
      </execution>
  </executions>
</plugin>

Please tell us about your environment:

• JavaPackager version:
• OS version: Arch Linux (DE: xfce4)
• JDK version: 18 with JavaFX
• Build tool:
  • [x] Maven
  • [ ] Gradle

I'd really appreciate your help. Thanks a bunch in advance :100:

[DBChoco]

Fixed by adding <customizedJre>false</customizedJre>. Sorry for the trouble.