Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-71

LDAP Studio installer creates bad shortcuts

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.6.0
    • Fix Version/s: 0.8.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      Windows XP Professional

      Description

      LDAP Studio installer created a shortcut without "Begin in" which forced LDAP Studio to create a new workspace directory on startup, instead of using the workspace on $

      {LDAP_STUDIO_HOME}

      .

      1. screenshot-1.jpg
        40 kB
        Boris Kock
      2. screenshot-2.jpg
        41 kB
        Boris Kock

        Activity

        Hide
        Pierre-Arnaud Marcelot added a comment -

        Thanks a lot for your help Leandro.

        Show
        Pierre-Arnaud Marcelot added a comment - Thanks a lot for your help Leandro.
        Hide
        Leandro de Oliveira added a comment -

        It's working as expected now, thank you. (I'm sorry for mispelling "Start in", I'm not using an english version of windows here...)

        Show
        Leandro de Oliveira added a comment - It's working as expected now, thank you. (I'm sorry for mispelling "Start in", I'm not using an english version of windows here...)
        Hide
        Pierre-Arnaud Marcelot added a comment -

        We have updated the Installer script. The installer now correctly sets the 'Start in' property.
        The LDAP Studio workspace has moved to ~username/.ldapstudio on all packages (Mac OS X, Linux and Windows).

        Show
        Pierre-Arnaud Marcelot added a comment - We have updated the Installer script. The installer now correctly sets the 'Start in' property. The LDAP Studio workspace has moved to ~username/.ldapstudio on all packages (Mac OS X, Linux and Windows).
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Ok, I've found how to set the "Start In" Field on a Shortcut in the Installer script.
        http://www.jrsoftware.org/isfaq.php#startin

        Stefan also found how to specify the workspace location in the config.ini file.

        The installer of the next release 0.8.0 will fix this issue.

        Show
        Pierre-Arnaud Marcelot added a comment - Ok, I've found how to set the "Start In" Field on a Shortcut in the Installer script. http://www.jrsoftware.org/isfaq.php#startin Stefan also found how to specify the workspace location in the config.ini file. The installer of the next release 0.8.0 will fix this issue.
        Hide
        Stefan Seelmann added a comment -

        Another approach is to add the parameter "osgi.user.area.default=@user.home/ldapstudio" to the <LS-Home>/configuration/config.ini. We need to investigate these options for all supported OS.

        Show
        Stefan Seelmann added a comment - Another approach is to add the parameter "osgi.user.area.default=@user.home/ldapstudio" to the <LS-Home>/configuration/config.ini. We need to investigate these options for all supported OS.
        Hide
        Boris Kock added a comment -

        Adding a pointer to the directory containing the LDAP studio executable "fixes" the problem.

        Show
        Boris Kock added a comment - Adding a pointer to the directory containing the LDAP studio executable "fixes" the problem.
        Hide
        Boris Kock added a comment -

        The LDAP studio shotcut properties field "Start in" does not contain a direction to the directory in which LDAP studio is located. This results in the creation of a new workspace instead of using the default workspace. After a restart the created connections are gone.
        This was detected in LDAP studio 0.7.0 under Windows XP professional.

        Show
        Boris Kock added a comment - The LDAP studio shotcut properties field "Start in" does not contain a direction to the directory in which LDAP studio is located. This results in the creation of a new workspace instead of using the default workspace. After a restart the created connections are gone. This was detected in LDAP studio 0.7.0 under Windows XP professional.

          People

          • Assignee:
            Unassigned
            Reporter:
            Leandro de Oliveira
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development