FISHEYE_INST Environment variable is not picked up by the run.bat or start.bat script

XMLWordPrintable

    • Severity 3 - Minor
    • 17

      Issue Summary

      When starting the Fisheye/Crucible using the $FISHEYE_HOME/bin/run.bat or $FISHEYE_HOME/bin/start.bat the FISHEYE_INST set on the Windows Environment variable is not picked up instead the FISHEYE_HOME is always taken as the FISHEYE_INST path.

      Steps to Reproduce

      1. Set FISHEYE_INST as an Environment variable
      2. From the FISHEYE_HOME try to start the Fisheye/Crucible using the $FISHEYE_HOME/bin/run.bat or $FISHEYE_HOME/bin/start.bat the FISHEYE_INST set on the Env variable is not picked up
      3. Instead, the FISHEYE_HOME is always picked up as the FISHEYE_INST path

      Expected Results

      The $FISHEYE_HOME/bin/run.bat or $FISHEYE_HOME/bin/start.bat should pick up the correct FISHEYE_INST value set on the Windows Environment variable

      Actual Results

      The $FISHEYE_HOME/bin/run.bat or $FISHEYE_HOME/bin/start.bat file always picks up the FISHEYE_HOME as FISHEYE_INST path

      Workaround

      This is caused because the JVM parameters are not included without double quotes("") in the $FISHEYE_HOME/bin/fisheyectl.bat file.

      Find and modify the Line set FISHEYE_JVM_FLAGS

      From

      set FISHEYE_JVM_FLAGS="-Dfisheye.library.path=%FISHEYE_LIBRARY_PATH% -Dfisheye.inst=%FISHEYE_INST% -Djava.awt.headless=true -Djava.endorsed.dirs=%FISHEYE_HOME%\lib\endorsed"
      

      To

      set FISHEYE_JVM_FLAGS="-Dfisheye.library.path=%FISHEYE_LIBRARY_PATH%" "-Dfisheye.inst=%FISHEYE_INST%" "-Djava.awt.headless=true" "-Djava.endorsed.dirs=%FISHEYE_HOME%\lib\endorsed"

            Assignee:
            Ajay Singh (Inactive)
            Reporter:
            Danny Samuel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: