org.forgerock / org.forgerock.opendj

25 Sep, 2009

1 commit

07 Apr, 2008

1 commit

15 Feb, 2008

1 commit

20 Aug, 2007

1 commit

17 May, 2007

1 commit

15 May, 2007

1 commit

08 May, 2007

1 commit

27 Apr, 2007

1 commit

23 Apr, 2007

1 commit

  • ad0e455b   The commit contains code for the following: ... Browse Dir » 
    - The Upgrader wizard panels (except the final progress panel) now pass real user data to the upgrader process.

- A RemoteBuildManager that handles querying for and downloading build files.  Also code for handling access through web proxies.

- The create-webstart-standalone script has been modified to generate a QuickUpgrade.jnlp file that is put into the 'install' directory as a peer to the QuickSetup.jnlp script.



git-svn-id: https://svn.forgerock.org/opendj/trunk@1676 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     

29 Mar, 2007

1 commit

  • 2db5e4d3   These refactorings are essential in anticipation of a new quicksetup application… ... Browse Dir » 
    … for the upgrader feature (issue 598).  These changes were reviewed by Josu. 

1.  Establish the concept of an Application (Install, Uninstall, Upgrade, Revert etc.) so that common drudgery (progress notification, message formatting, look and feel, user input, file management etc.) can be handled by a common base class (newly created AbstractApplication).

2.  Establish clearly defined interface between the framework (QuickSetup) and the applications.

3.  Replace classes currently defined in each application's package having lots of commonality with common classes (see new classes in org.opends.quicksetup).

4.  Miscellaneous cleanup mostly handled by my IDE (fix Javadoc problems, optimize import statements etc.)

This commit also:

- made ProgressSteps an interface that the application specific enums implement.

- moved the uninstaller specific user data back into a UninstallUserData object.  For now I've left the installer's UserData to be more of a default since it has lots of properties I imagine would be useful for the upgrader.

- added a new system property org.opends.quickstart.Application.class for specifying the application class of the Application to be instantiated.  I've done this to remove some of the logic involved in determining which application to create in QuickSetup (if (isWebStart())..., if (isInstaller())...).  The create-webstart-standalone script now generates this property as do the *Launcher classes.  Applications are now created in the Application.create() method.

- QuickSetup now creates the application during the init phase rather than waiting until the launch*.  This so that the application can supply the user data necessary (specialized user data if necessary as is done by the uninstaller application). 


git-svn-id: https://svn.forgerock.org/opendj/trunk@1537 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     

14 Mar, 2007

1 commit

  • e4514af9   Fix for issue 1296. ... Browse Dir » 
    QuickSetup is not using the latest version in www.opends.org in certain scenarios because we are using the offline-allowed element.  If this option is specified the application is launched and then the checking for updates is done.  If the checking times out the copy stored in the cache is used.  The fix consists of removing this option (in the context of opends.org we are always running online).


git-svn-id: https://svn.forgerock.org/opendj/trunk@1409 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

10 Mar, 2007

1 commit

21 Nov, 2006

1 commit

20 Nov, 2006

1 commit

19 Nov, 2006

1 commit