directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRSTUDIO-130) Rename package names and plugin IDs
Date Fri, 08 Jun 2007 16:09:26 GMT
Rename package names and plugin IDs
-----------------------------------

                 Key: DIRSTUDIO-130
                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-130
             Project: Directory Studio
          Issue Type: Task
    Affects Versions: 0.8.0
            Reporter: Stefan Seelmann
             Fix For: 0.9.0


Important: Before starting please check that there are no pending commits.

(3) Rename Java package names
I would recomment to replace org.apache.directory.ldapstudio with
org.apache.directory.studio for all plugins. As in (2) I would like to
prefix the browser packages with "ldap" and to modify the schemas
packages to schemaeditor:
  org.apache.directory.studio.ldapbrowser.
  org.apache.directory.studio.schemaeditor.
Impacts:
* All connectons in the LDAP browser will be lost. We use the
java.beans.XML(De|En)coder to save the ConnectionParameter objects in
xml, it uses the FQCN to save/load the connections.
Resolution:
* We have to improve the ConnectionManager to replace all old package
names with the new package names in the connections.xml


(4) Rename plugin IDs
We should rename the plugin IDs according to the package names.
Impacts:
* All dialog settings will be lost. Each plugin has its own directory in
the workspace under .ldapstudio/.metadata/.plugins/ according to its
plugin ID. When modifying the plugin ID the old settings are no more
accessible.
* All preferences will be lost. Each plugin has its own preferences file
under .ldapstudio/.metadata/.plugins/org.eclipse.core.runtime/.settings
according to its plugin ID. When modifying the plugin ID the old
prefernces are no more accessible.
* All connections will be lost because the connection.xml file is stored
under the plugin specific directory.
* Trouble with updates, see (7)
Resolution:
* Ignore first and second point, advise the user to redo his/her
preferences.
* We have to improve the ConnectionManager to copy the connections.xml
from the old state location to the new one.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message