Changes in base64 http://src.iws.cs.ovgu.de/source/rss/forgerock/opendj2/resource/bin/base64 en Copyright 2005 Java Fix for OPENDJ-222 : Renamed environment variables to OPENDJ_... Updated scripts so that if OPENDJ_JAVA_HOME and OPENDJ_JAVA_ARGS are not defined, we look at the legacy OPENDS_... ones. /forgerock/opendj2/resource/bin/base64 - 0f8553e2af5fc49a510ecfcfc93e66d06713f631 ludo Updated the copyright statement to reflect that Sun owns the full copyright on the project files. /forgerock/opendj2/resource/bin/base64 - 65e99be301d5a19db33f25841f671756e8dbb9b5 ludovicp 2730: New - The setup command should perform some basic memory tuning Note: this issue is not fully covered by the proposed modifications but all that is missing in order to fix it is to figure out which are the default memory values that we want to propose in the setup. 2620: Server should be started as server JRE and clients should be started as client JREs The proposed solution goes beyond fixing the two issues and proposes a manner for the user to set specific java arguments (and use a specific JVM) for every command-line. Today the user can specify the JVM to be used using the OPENDS_JAVA_HOME environment variable and the java arguments by using the OPENDS_JAVA_ARGS environment variable. In the case of the JVM this covers most of the use cases (in general we will use the same JVM for all the command-lines). However this is quite limiting in the case of the java arguments we pass. For instance in general we want to run the server (start-ds command-line) using the server mode of the JVM but other command-lines using the -client mode of the JVM. In the same manner we might want to have a bigger heap when running the server than when we are running a "lightweight" utility as dsconfig. The proposed solution is to have a properties file called java.properties where the user specifies the different JVM and java arguments to be used for every command-line. Once the user has edited this properties file, (s)he must run a command-line called dsjavaproperties that will update all the scripts to use the arguments specified in that properties file. NOTE: there are a number of command-lines (import-ldif, export-ldif, backup, restore) where the user will be able to specify different java arguments (and different JVM) to use depending on whether the command-line is run in online or offline modes. You can see the comments on java.properties to get more information about this and in general about the different properties that can be set. The modification in the setup basically try to check if the JVM that is being used to run the setup (the one that will be used by default) supports the -client and -server options. Depending on the results of these checks the setup will update the java.properties file and then run dsjavaproperties to update the scripts. /forgerock/opendj2/resource/bin/base64 - 27f8adec83293fb8bd3bfa37175322b0ee3bb933 jvergara Add a tool that can be used to base64 encode or decode information. The source can be provided as a string, contained in a file, or piped in via standard input, and the result can be sent to standard output or written to a file. /forgerock/opendj2/resource/bin/base64 - 49050c663d9aaca6919a5a77cd739ea9ddcd9e03 neil_a_wilson