Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-3391

Installer should not require UI to report errors in automated mode

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.0.Alpha2
    • 9.0.0.Alpha1
    • installer
    • None
    • Hide

      1. Remove plugins folder form installer jar so installation would fail.
      2. Run installer without UI like:

      DISPLAY="" java -jar installer-XXXX.jar

      3. ASSSERT: It shows errors about missing artifacts to standard output

      Show
      1. Remove plugins folder form installer jar so installation would fail. 2. Run installer without UI like: DISPLAY="" java -jar installer-XXXX.jar 3. ASSSERT: It shows errors about missing artifacts to standard output
    • Hide

      run installer as

      java -DTRACE=true -jar installer-XXXX.jar

      to see error messages for p2 director

      Show
      run installer as java -DTRACE= true -jar installer-XXXX.jar to see error messages for p2 director
    • NEW

    Description

      Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available.

      Exception in thread "IzPack - Unpacker thread" java.lang.InternalError: Can't connect to X11 window server using '' as the value of the DISPLAY variable.
      	at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
      	at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
      	at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74)
      	at java.lang.Class.forName0(Native Method)
      	at java.lang.Class.forName(Class.java:191)
      	at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102)
      	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81)
      	at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:120)
      	at java.lang.Class.forName0(Native Method)
      	at java.lang.Class.forName(Class.java:191)
      	at java.awt.Toolkit$2.run(Toolkit.java:869)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:861)
      	at javax.swing.ImageIcon.<init>(ImageIcon.java:186)
      	at javax.swing.ImageIcon.<init>(ImageIcon.java:205)
      	at com.izforge.izpack.installer.ResourceManager.getImageIconResource(Unknown Source)
      	at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:614)
      	at java.lang.Thread.run(Thread.java:745)
      

      Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.

      Attachments

        Issue Links

          Activity

            People

              nivologd@gmail.com Denis Golovin (Inactive)
              nivologd@gmail.com Denis Golovin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: