Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8125821

The Windows launcher generated by the packager fails when called with no parameter

    Details

      Backports

        Description

        I produced a Windows self-contained bundle with FX packager. At top level it contains an application executable, say sb.exe.
        If in a terminal I call "sb.exe toto.fxml" it opens the provided file, fine.
        But if I call "sb.exe" it returns immediately, exit code 127. As a consequence I cannot start my app by double clicking the desktop icon, annoying.

        I use Win 7 64-bit. I produce my self-contained bundle using Java 7 U10 b08 (or b09) 32-bit.

        For some reason doing exactly the same on Linux does well: the generated native launcher starts the app on a blank file when called with no param, or starts the app on the file provided as a parameter.

        To give it a try by yourself I can provide you a bundle (big) ar detail how to produce it from the scenebuilder repo.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mhowe Mark Howe (Inactive)
                  Reporter:
                  yjoan Yves Joan (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Imported: