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

Runtime not respected with INI-configuration while creating native bundle

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 8u60, 9
    • Fix Version/s: 9
    • Component/s: deploy
    • Subcomponent:
    • Introduced In Version:
    • CPU:
      x86
    • OS:
      windows_8

      Backports

        Description

        FULL PRODUCT VERSION :
        java version "1.8.0_60"
        Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
        Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

        ADDITIONAL OS VERSION INFORMATION :
        Microsoft Windows [Version 6.3.9600]

        A DESCRIPTION OF THE PROBLEM :
        Hi, I'm the maintainer of the javafx-maven-plugin.

        After upgrading to newer java-version, the generated .cfg-file changed the format, it is a simple "INI-file" now. That's not the problem, but when I set the bundle-argument "runtime" to null or empty string (for not having any bundled runtime), the generated native bundle is not having the runtime-folder, BUT the generated .cfg-file does contain "app.runtime=$APPDIR\runtime".

        I documented my findings at github:
        https://github.com/javafx-maven-plugin/javafx-maven-plugin/issues/167

        The problem, I found, seems to be the new introduced ini-file-format (which does not respect my setting):
        http://hg.openjdk.java.net/openjfx/8u-dev/rt/file/e885b6e60687/modules/fxpackager/src/main/java/com/oracle/tools/packager/AbstractImageBundler.java#l154

        The problem is not windows-only, it happens on ubuntu/linux too (but there JRE will be bundled).

        REGRESSION. Last worked in version 8u45

        STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
        on windows:
        * set runtime-parameter to empty string: <fx:platform basedir=""/>
        * generate native bundle with jdk 1.8 update 60 (or above)
        * try to run generated native launcher

        EXPECTED VERSUS ACTUAL BEHAVIOR :
        EXPECTED -
        launcher starting with system JRE
        ACTUAL -
        launcher not working, says something about not being able to start JVM

        REPRODUCIBILITY :
        This bug can be reproduced always.

        CUSTOMER SUBMITTED WORKAROUND :
        Only changing to "older" cfg-file-format makes it possible to launch windows native launcher

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dcherepanov Dmitry Cherepanov
                  Reporter:
                  webbuggrp Webbug Group
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: