OPENDJ-1133 RPM : wrong files under /usr/share/doc/opendj-*version* - removed rfc2605.txt from documentation folder and restored in its initial folder /snmp/mib/ (RPM) - removed README file from RPM-DEB package (it contains informations about installation process and is unused for packages.)

Fix for OPENDJ-1136. Removing OpenDS SVR4 package files that are no longer maintained. Corrected minor build constants.

CR-2281 Fix for OPENDJ-1021: Remove obsolete opendj/bin/README_Windows.txt

OPENDJ-1114 Improve the debian package - Changelog added

Since jabx and xjc are now part of JDK (starting with 1.6), we no longer need the jars nor the ant task. Building directly with xjc is preferred and this also makes the war file lighter.

OPENDJ-1114 Improve the debian package - Original data are copied under build/deb/ folder as the process to build the deb package implies to modify the source. - Opendj init script has been modified. Indeed, under debian OS (and others) the /var/run/ folder is deleted at reboot, deleting by the same way our pid file, making the service wobbly. - As linux distro use the same opendj file, a new folder was created under resource to store the shared file between them. - At last, modified post/prem/specFile as well as the fact to create a symlink on an existing one throws an error. (same when you try to remove one from no-existing)

Partial fix for OPENDJ-1114 Improve the DEB package - copyright added - doc section added (to complete)

Partial fix for OPENDJ-1031 (DEB part)

Fix for OPENDJ-1069, no longer delivering the instance.loc file. Now that the .bat files can cope with the absence of the file, we can remove it completely. CR-2142

CR-2123 OPENDJ-1068 create resources for rpm packaging - added init.d script to RPM package.

Fail the package-MSI target unless on Windows

Remove wix.dir, rely on PATH

CR-2100 Fix OPENDJ-1108 Provide native packaging for Windows

Fix relative to OPENDJ-1063 and OPENDJ-1032 - Fixed the doc's section (doc files are no longer duplicate)(OPENDJ-1032) - Target no longer fails when build path contains spaces (OPENDJ-1063) - Out of concern for clarity, added docFiles to resource/rpm.

OPENDJ-1032 RPM package should be built in a different way for more visibility.

CR-1977 Fix for OPENDJ-1005: Move server doc sources alongside other server code

Backport fix for OPENDJ-1026: Support the ability to specify the license file when building OpenDJ

OPENDJ-1011: Update install.txt and install.html In the end, it's simpler long term to include the install instructions in the README, and remove these extra files. With additional review from Ludo by mail, I've also fixed up a few small things in the README. I'm leaving the SVR4 related changes to Ludo.

Fix for OPENDJ-925, OPENDJ-926, and overall schema management. Review CR-1806. Back a few years ago, when we did the SVR4 package, we split the schema into read-only (Install) and writable (Instance). With the template model in 2.6, the whole schema is under config, and we should never edit/change the one in the template. So, I've removed all code related to the 2 locations for schema, reverted some I10N messages to their previous versions, and tidy up code and tests. All unit-tests are passing. And it's also possible to change the instance.loc and run setup and have a fully functioning server :-)

Trivial fix on deb package about description (lowercase to CamelCase).

Fix issue OPENDJ-108, CR-1791. Also fix minor issues with URLs in the install.html and .txt files.

Minor fix on deb packages. - added message when buildinfo is not found. - excluded .app / bat files.

OPENDJ-946 Package build fails when special chars are contained in the VERSION_QUALIFIER. - The packages name for Deb/RPM follows the rules given by their respective documentation. - Adding a VERSION_QUALIFIER containing special chars no longer make fail the package build.

OPENDJ-938 Package: package name should be "opendj" instead of "OpenDJ" - A new var has been created in PRODUCT file. The 'Release number' should start at 1 for the RPM and the 'debian revision number' (.deb) as well.

Fix for OpenDJ-909 : ControlPanel.app exits during startup. There are a number of issues with the Mac Apps, and this commit fixes most of them, but we should also change the icon name and picture once we have a logo for OpenDJ. The version and revision numbers are now automatically set when packaging. The -client JVM option is deprecated and thus removed. And we properly set the ServerRoot to allow ControlPanel to work when double clicking the icon. Note that Mac App are dependant on the JavaApplicationStub that only supports Java6. We fine for now, since OpenDJ is built with target 1.6, but we will need to redo the Apps when/if we switch to 1.7 by default.

OPENDJ-844 Patches don't affect ControlPanel.app OPENDJ-842 On Windows, the setup command hangs when the length of the install path is too long Code review and initial idea: violette Now that the application starts with the single bootstrap jar, MacOS X can take advantage of this by referencing it statically in the plist files. In other words, it is no longer necessary to build the plist files dynamically. Info.plist: Hardcoded the path to bootstrap.jar build.xml: Removed the code that appended the jars to the **/Info.plist files for MacOS X.

OPENDJ-842 (CR-1699) On Windows, the setup command hangs when the length of the install path is too long In order to avoid getting errors like "The input line is too long" on windows, a common way to fix this is to provide a "bootstrap" empty jar which contains only a MANIFEST.MF file listing all the application's jars in the "Class-Path" attribute. This URL describes well enough the problem: http://ant.apache.org/manual/Tasks/manifestclasspath.html build.xml: In "prepackage" target, build bootstrap.jar. _script-util.bat, _script-util.sh: Replaced appending all the jars under libs with just the bootstrap jar. Utilities.java, Utils.java, UpgradeUtils.java: In getInstallPathFromClasspath(), extracted getInstallPath() and simplified its code a lot. Installation.java, Installation.java: Changed OPEN_DS_JAR_RELATIVE_PATHS into OPEN_DJ_BOOTSTRAP_JAR_RELATIVE_PATH.

OPENDJ-904 RPM/Deb packages should not restart server after package update. - Modified RPM/Deb scripts - Modify RPM build number.

svn merge https://svn.forgerock.org/opendj/trunk/opends@8851 https://svn.forgerock.org/opendj/branches/native-packaging@8851 .

Use Maven to build OpenDJ server Trying to bring opendj server the most possible under maven. Here maven-antrun-plugin is only used to generate the java files from our resources. I am sure there are many glitches that need to be fixed in this file. We'll fix them over time. It is not ready to be used as prime build system yet. For example, no tests are run yet, or several resources are missing (.properties files, other??). My goal is to bring opendj server under Sonar in order to see code coverage data. Use "mvn -f pom-maven.xml clean install" to compile. build.xml: Renamed compileadmin target to generateadmin.mvn -f pom-maven.xml clean install Added generatesources target depending on dynamicconstants, generatemessages and generateadmin. In generateadmin target, pass down admin.src.dir property to generateadminsubtask. pom-maven.xml: ADDED Inspired from pom.xml.

Fix error in build.xml. Ant should be taken from ant.dir (within the workspace)

OPENDJ-844 (CR-1527) Patches don't affect ControlPanel.app build.xml: Added code to automatically append the classpath entries to the **/Info.plist files for MacOS X. This includes the classes directory and all the jars too. Info.plist: Removed hardcoded paths. Added classes directory first in the classpath to allow patches to work.

Removed the test jars from the final OpenDJ zip package.

OPENDJ-830 (CR-1505) Implement authentication and authorization for HTTP connection handler Implemented authentication with a synchronous username search + bind. To come next: asynchronous username search + bind. HTTPAuthenticationConfig.java: ADDED build.xml, ivy.xml: Added some tests jars + updated grizzly to the newly released 2.3 stable version. CollectClientConnectionsFilter.java: Added HTTPAuthenticationConfig instance member to configure the HTTP auth from the JSON file. Added many methods to handle HTTP auth in a synchronous way. Will have to change this code to run asynchronously for performance. HTTPClientConnection.java: Changed a few signatures and types to handle more than Search operations. HTTPConnectionHandler.java: Added methods parseJsonConfiguration(), getAuthenticationConfig(), asString() and asBool() to read the config for HTTP Authentication. SdkConnectionAdapter.java: Handled several messages being sent through the same connection. Extracted methods enqueueOperation() from searchAsync(). Implemented bindAsync(). Adapters.java, Converters.java: Added new conversion methods. Renamed local variables to correctly use camel case. ConvertersTestCase.java: Removed try / catch / empty anti pattern.

Cleanup removing trailing spaces

Removing some repetition for opendj.runtime.jars . This adds more semantic before adding opendj.test.jars too.

(CR-1489) Build offline with Ivy Adding back offline building despite checking for the latest snapshot jars. Example command line to invoke for building offline: ant resolve -Dbuild.offline=

OPENDJ-808 Implement a simple commons REST based HTTP connection handler build.xml: By popular demand, stripped out the version number from the jars under the lib directory. This way, they now have a stable location, whatever the version they are on.

OPENDJ-808 (CR-1439) Implement a simple commons REST based HTTP connection handler Added support for Ivy from the ant file build.xml. "Apache Ivy™ is a popular dependency manager focusing on flexibility and simplicity." As part of the build, Ivy gets downloaded and installed as ext/ivy.jar, if it was not already installed. Ivy will then download all the dependencies and transitive dependencies from forgerock artifactory, maven central and oracle public maven repo as specified in ivy.xml and ivysettings.xml and put them under the lib/ directory. This step is similar to what maven does. Finally, I removed je.jar and mail.jar as they also get downloaded by Ivy now. Ivy uses a download cache under ~/.ivy/cache to prevent always downloading the jars from internet. I made sure that after a successful build, rebuilding without the network works fine. I also made sure the built zip contains only thebinary jars, and not sources jars or javadoc jars. Here is now the content of the lib/ directory in the OpenDJ-2.5.0.zip file: $ ls build/package/OpenDJ-2.5.0/lib/lib/ activation-1.1.jar grizzly-framework-2.3-rc6.jar grizzly-http-2.3-rc6.jar grizzly-http-server-2.3-rc6.jar grizzly-http-servlet-2.3-rc6.jar grizzly-rcm-2.3-rc6.jar javax.servlet-api-3.1-b05.jar je-5.0.48.jar launcher_administrator.exe mail-1.4.1.jar opendj_service.exe winlauncher.exe Please also have a look at the attached out.patch file since crucible does not allow me to upload it as a patch. It contains changes to SVN properties and removed files.

build.xml: Fixed indentation in several places.

CR-920 Fix for OPENDJ-651: ./build.sh dsml fails if path to sources contains spaces

Revert r8334, as the problem seems to be reproduceable as described in OPENDJ-651

Attempt to get more information when Jenkins fails

Revert r8332: Build on Jenkins seems to fail in the same way with or without -npa

Test XJC task without -npa

Fix OPENDJ-502 DSML gateway not correctly forwarding modifications to userCertificate;binary attributes

CR-658 Fix for OPENDJ-566: Add log reference to OpenDJ docs

Fix OPENDJ-525: Remove compiler warnings when building using JDK7

Disable code coverage since Emma is no longer maintained and does not support JDK7.

Fix OPENDJ-407: Upgrade version of Ant included in OpenDJ server sources

Fix issue OPENDJ-396: Remove support for ServiceTags

Fix OPENDJ-378: Remove activation.jar as it's bundled with Java 6

Fix OpenDJ-222: Remove more references to OpenDS. Finally update build files and refresh the SVR4 copyright notice (with latest JE license)

Fix OPENDJ-324: Remove NDB backend implementation

Fix the wiki.home reference

Fix for issue OPENDJ-214. Rebranded as OpenDJ and now uses product-name variable.

Fix snmptest dependancy

Add support for SVR4 packages for OpenDJ. Package name is opendj. It's a single package and has integration with SMF. Default installation is /usr/opendj. Once packages are installed, root must run configure to setup the Instance location (/var/opendj) and owner. And the owner must run setup.

Fix build issue aroung generation of snmp MIB when the project path contains space. Found and corrected by Peter Major.

Building OpenDJ

Changes in OpenDS factory to build with Java 6 only. Minimal version is Java 1.6.0 Update 10. Also fixes Message file generation to allow custom location.

Fixing build factory to work properly with JDK6u18, MacOS X and NetBeans.

display java version also for the build part

- bump the MEM property to 512Mb to avoid OOM when building on 64b VMs such as Apple MacOS 10.6 SE 6.

Fix find/replace collateral damage in previous commit...

Display output of java -version before running unit tests. This can be useful when debugging automated builds.

Catalan translations from the community

polish translations

Un-commit the last changes made to this file.

Fix for issue 4326 (Allow setup of a Server without Data suffix) If the user does not specify the option baseDN (in the command-line setup) or leaves the base DN text field empty (in the graphical setup), no b ase DN will be created. Fix some issues with the installer, that on Mac OS used to make the terminal to lose focus before the confirmation of the setup.

Fix for issue 2531: Removed all AspectJ dependencies.

Fix 4045 : start-ds -F doesn't return snmp build info

Today if a user makes a mistake in DynamicConstants and introduces a coding style error, this error will not be spotted on the first run of the precommit target (but it will on the second and so on). This fix guarantees that the checkstyle will be executed AFTER DynamicConstants is generated. There is a change of behavior that I consider harmless but maybe I am missing something: the clean of the build package is made before the checkstyle is executed. This adds an extra second or so to spot errors on checkstyle, but it seems to me cleaner to do a clean and then do the checkstyle (to be sure that no error were introduced in the dynamically generated java files).

Revert the two files that were wrongly committed in revision 5555.

Allow productization in the name of the Window service by allowing to pass the name and description of the service name in ConfigureWindowsService. Remove references to OpenDS in the messages displayed by the Windows Service command-lines.

svn merge -r5333:5417 https://opends.dev.java.net/svn/opends/branches/b2.0

- fix rebuild target which got broken by changes introduced in revision 5132.

Fix for 3907: Provide pkg(5) delivery This modification implements a factory to build a pkg(5) delivery (aka IPS multi-platform) for OpenDS. This factory adds the following targets: * package-pkg-make-image: build a pre-installed installation image * package-publish: publish OpenDS into an IPS repository The pre-installed installation image contains * OpenDS core runtime * OpenDS Directory Services Markup Language (DSML) Gateway as add-on

fix incorrect svn revision and add svn url in start-ds -F

Fix for issue #3863 : dsconfig exception when trying to set the subject-attribute in Subject DN To User Attribute Certificate Mapper

- land NDB Backend implementation.

- fix scary message

- remove useless target dependencies to shorten build output and time.

- fix typo

do not copy english version

L10n localization of the generated files

Fix 3534: Provide native Solaris packages (fix also 3533: upgrade fails starting server adding entry ds-cfg-key-id)

The commit will bring the following features : - An updated version of the underlying database. BDB JE 3.3 is now used. - Attribute API refactoring providing a better abstraction and offering improved performances. - A new GUI called the Control-Panel to replace the Status-Panel: the specifications for this GUI are available on OpenDS Wiki and contains a link to a mockup. See <https://www.opends.org/wiki/page/ControlPanelUISpecification>. - Some changes in the replication protocol to implement "Assured Replication Mode". The specifications are on OpenDS Wiki at <https://www.opends.org/wiki/page/AssuredMode> and section 7 described some of the replication changes required to support this. Assured Replication is not finished, but the main replication protocol changes to support it are done. As explained by Gilles on an email on the Dev mailing list (http://markmail.org/message/46rgo3meq3vriy4a), with these changes the newer versions of OpenDS may not be able to replicate with OpenDS 1.0 instances. - Support for Service Tags on the platforms where the functionality is available and enabled. Specifications are published at <https://www.opends.org/wiki/page/OpenDSServiceTagEnabled>. For more information on Service Tags see <http://wikis.sun.com/display/ServiceTag/Sun+Service+Tag+FAQ>. - The Admin Connector service. In order to provide agentry of the OpenDS server at any time, a new service has been added, dedicated to the administration, configuration and monitoring of the server. An overview of the Admin Connector service and it's use is available on the OpenDS wiki <https://www.opends.org/wiki/page/ManagingAdministrationTrafficToTheServer> - Updates to the various command line tools to support the Admin Connector service. - Some internal re-architecting of the server to put the foundation of future developments such as virtual directory services. The new NetworkGroups and WorkFlow internal services which have been specified in <https://www.opends.org/wiki/page/BasicOperationRoutingThroughNetworkGroup> are now implemented. - Many bug fixes... This set of changes may have an impact on current clients and deployments, however it should be possible to upgrade existing 1.0 instances. Some of the changes impacting the clients include : - Scripts using the command line tools including dsconfig will need to be updated (usually to remove some no longer required options).

These changes are separating the current delivery into an "Install Layout" (the binaries) and an "Instance Layout" (the user data).

Fix for issue #3456 : Add a new property to build.xml : wiki.home

Fix for 3259: No messages support in example plugin Changes by file: . resource/admin/example-plugin/ExamplePlugin.java - support for messages - fix for PluginResult.Startup refactoring . resource/admin/example-plugin/example_plugin.properties - 3 messages used in the example plugin (english/default) . resource/admin/example-plugin/example_plugin_fr.properties - 3 messages used in the example plugin (french) . resource/admin/example-plugin/build.xml - automatic generation of messages from properties files located in resource/messages while keeping package name. (eg. resource/messages/my/example/example_plugin.properties will generate a message class with package name "my.example") . resource/Messages.java.stub - forced underlying properties files to be located in /messages within jars file (eg MY_JAR_FILE:/messages/example_plugin.properties) - support for messages available from extensions' classloaders . src/messages/src/org/opends/messages/Message.java - typo in javadoc . build.xml - added message template used by generator in the build-tools.jar - added the "resource/messages" directory at the root of the example plugin - added example properties files in the example plugin zipfile . src/build-tools/org/opends/build/tools/GenerateMessageFile.java - stopped assuming messages are targeted in package name org.opends.messages - template for message class generation now retrieved from the build-tools.jar when generating messages for extensions - for user messages, set destination files automatically based on the source full filename and apply basic pattern (eg. source=resource/messages/my/example/example_plugin.properties sets destination to src-generated/my/example/ExamplePluginMessage.java)

This patch adds index buffering capabilities to the JE backend as to avoid using a fixed lock timeout for subtree delete and mod DN operations. Previously, any index modifications to subordinate entries of the affected operations will be performed with dn2id and id2entry modifications. This creates multiple random access to index database keys which could cause deadlocks in face of multiple parallel operations. With this fix, all index modifications are buffered up until the end of the operation so that each key of each index will be accessed once and in order. This maintains the DB access ordering in the JE backend of dn2id, id2entry, dn2uri, indexes in config order, VLV indexes in config order, and finally id2children and id2subtree. Since deadlocks should no longer occur in the JE backend, JE lock timeouts are now disabled at the JE environment level instead of the txn level. With this change, the performance of subtree deletes and mod DN operations have increased dramatically. In order to add buffering capabilities to the VLV index, the format of the index records had to be changed. Previous DBs with VLVs configured will no longer be compatible with this new revision. Cursors operations for subtree mod DN and delete operations are now taken with READ_COMMITTED JE isolation level to avoid locking un-affected entries and possibility causing deadlocks. Write operations affecting the DN2ID and ID2ENTRY databases will aquire an write lock directly as early as possible to avoid deadlocks. A issue is also fixed where the debug log genereated during unit tests does not include stack traces. Fix for issues 2980, 2186, 2979

Fix for Issue #3092 (bundled installation doc should also be available as text file)

Put back the example-plugin target in build.xml

Add SNMP source code in checkstyle list

- enable checkstyle for dsml package.

Update the SNMP Unit tests. Delete the nbproject (will be available as a zip on https://www.opends.org/wiki/page/BuildingAndRunningOpenDSWithinNetbeans)

* Fix for Issue 218 : Monitor Information Available via SNMP * Update the nbproject to include the snmp source code

Updated the copyright statement to reflect that Sun owns the full copyright on the project files.

- Issue #2004 (automatically generate HTML configuration guide) Implementation of the Brian's mock-up 2 Configuration Reference are now generated in build/docgen: - one without the LDAP mapping - one with the LDAP mapping - Fix for Issue #2912 ("core" category should be "core server")

Fix issues 2831 and 1948. Change local DB backend configuration so that db-directory and import-temp-directory properties now name a parent directory within which a sub-directory is created having the same name as the backend-id. This simplifies configuration and reduces the risk of name collisions.

Removed "bad path element" warnings from the DSML gateway compilation.

Fix for issue 2822 (Config file should be read-protected) Update the permissions of the root file of the installation (in the diffs is proposed to be 700). This is done in build.xml when generating the zip file and in the web start installer.

Move configuration stylesheet from resource/config to resource/admin

This is a new feature : automatically generate HTML configuration guide (issue #2004) This new doc generation is included in the build.xml : - a new target has been added : "docgen" - this target is called at the same level as the javadoc target (i.e. from "all" and "nightly" targets) - the doc is generated at : build/docgen/configuration_guide (note that Brian is still working on the mockup, so the headers of the pages will have a nicer look)

remove temporary files for RPM built

Fix for issue 2830: Improvements to build "test" target. This change modifies the Ant "test" target so that it is as lightweight as possible but forgiving for first-time users. The test target now checks to see if there is an OpenDS.zip package in build/packages and, if there is, it simply recompiles the Java source files (no message generation or admin framework code generation). If no OpenDS.zip package is found then it automatically invokes the "package" target so it is now possible to do the following: ./build.sh clean ./build.sh test

change rpm spec file generation ant task from typedef to taskdef

Fix for issue #2640 (Provide RPM delivery)

Fixes for : 2786 : DSML Gateway misses saaj jars 2774 : DSML gateway war file contains many unnecessary files

Issue 2650: import-ldif command should give information about JRE version and settings Change the server startup and import-ldif startup message to display runtime information. See issue for details.

- aggregate MEM property and bump its value to 256Mb.

Remove jvm attribute from profiling session to support every NB6.0 environments

I use this bug id (138) as an umbrella for a list of bugfixes/improvements for the DSML gateway. Here is the detail file by file: . DSMLAbandonOperation -> error handling : abandon Id is now mapped to an unwilling to perform error (was IOException) . DSMLDeleteOperation -> added matchedDN in response (was missing) . DSMLServlet -> added schema validation during JAXB parsing -> dropped usage of an internal JAXB class (useless and risky as this class was renamed in Java 6) -> removed doGet method (useless/cleanup) -> check that if authorization is tagged in http request (bindDN, passwd) are both provided and valid -> better error handling : safer processing with appropriate error messages instead of global try/catch with generic message - in case of parsing error, the request in reparsed with SAX instead of JAXB in order to extract requestID and build appropriate response - in case of processing exception, a mapping (hard-coded) is performed and set in the error response message -> fixed processing onError: default behaviour was to stop once a request failed but the specification defines to continue . DSMLSearchOperation -> added missing filters : "and", "or", "not", "substrings", "greaterOrEqual", "lessOrEqual", "approxMatch", "extensibleMatch" ("equalityMatch" and "present" were provided) -> fixed ability to return attribute names only (typesOnly) . build.xml -> added schema in DSML war file to enable JAXB schema validation

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.

This relates to issue 2661 "public APIs must not reference private classes". The classes in org.opends.messages need to be made public so that they can be referenced from other public APIs. This change adds the PublicAPI annotation to the classes defined in this package as follows: * the org.opends.messages package is VOLATILE * the org.opends.messages core classes (Message, MessageDescriptor, MessageBuilder, Category, and Severity) are all UNCOMMITTED * the class org.opends.messages.MessageDescriptorRegistry is PRIVATE (it's only used in unit tests) * generated message classes are PRIVATE In addition minor cleanup was made to the classes where appropriate to make them suitable for public APIs: * used "final" where possible * reduced visibility of classes, methods, and members where appropriate * fixed some potential bugs spotted during this clean-up: class members not being initialized (the "final" keyword is useful for spotting this!) * added missing javadoc * I've removed the third-party and user-defined message generation since we could see know way in which they could be easily used without impacting core OpenDS source

Fix for 1732 - provide bundled installation documentation. This commit adds installation instructions in an html file called install.html to the top level install directory. The opends logo is included as it appears at the top of the html page

- add missing nodetach in run-server and nb-debug-server targets. - enable debug in nb-debug-server target. - add new nb-profile-server target for one click server profiling from NetBeans. - fix formatting and trailing spaces.

Added 2 targets to run DS and dsconfig : "run-server" and "run-dsconfig", that allow to run the Server (or dsconfig) without using the shell script, e.g. from Netbeans. Added 2 targets to debug DS and dsconfig from Netbeans : "nb-debug-server" and "nb-debug-dsconfig" that allows to both run the Server (or dsconfig) in debug mode, and attach them automatically to the Netbeans debugger. So you only have to set your breakpoint.

Update the ant build script so that it correctly sets the maximum amount of memory available when running the compileadmin target.

Add copymessages target so that it can be called from an IDE.

Since the administration backend is an LDIF backend, remove the adminDb directory from the layout.

- add Mac native application bundles for QuickSetup, Uninstall and StatusPanel. note that these bundles are not self contained and cannot be arbitrary moved outside of OpenDS distribution or installation location.

After some discussions it has been decided to merge the setup and uninstall commands so that we have the behavior that we had before. So with this changes, in order to work in CLI mode the option --cli must be specified.

removed integration test artifacts

commented out broken checkstyle invocation

Add a new build-tools source stub for the netscape.ldap.LDAPSocketFactory class that is part of the Mozilla LDAP SDK for Java. Also, use this source stub to create the org.opends.server.protocols.internal.InternalMozillaLDAPSocketFactory class which implements that interface and allows users to more easily use the Mozilla LDAP SDK for Java to invoke internal operations in the server. Note that the source stub is used only to allow our code to compile. Anyone that wants to use the Mozilla LDAP SDK for Java to perform internal operations will need to supply the full library containing the LDAP SDK for Java.

Revert the change to build.xml made in revision 3009, as it has broken the rebuild target.

As a way to speed up an incremental build, I've updated the compileadmin target to only generate the config java source if the definition files have changed.

Partial fix for issue 1449: administration framework aggregation support This change adds support for "aggregation" properties, which are properties which reference other managed objects (see issue 1449 for more details). Subsequent changes will add server-side and client-side referential integrity support, as well as migrating components over to using them (this will be post MS1.0).

The following changes are targetted to fix a certain number of issues related to the setup command line: * 1257 setup cli/gui symetry -- allow to start after slient install * 1264 silent install option is not silent * 1326 Update setup CLI to integrate common install scenario (partial fix) * 1404 different CLI/GUI behavior running setup * 1859 spin off GUI specific CLI commands * 2184 setup quite/no-prompt * 2185 setup --cli -Q throws error The changes basically consist on splitting the current setup command-line into two (the same way we have done for the uninstall). Know we will have one command to launch the setup in CLI mode (setup and setup.bat) and one command to launch the setup in GUI mode (setup-gui and setup-gui.bat). The behavior of the graphical interface has not changed. However the capabilities of the CLI setup have been extended to allow to match those in the graphical interface (excluding the replication configuration capabilities): * Configure the LDAPS and StartTLS on the server. * Start the server.

Fixed testhelp for -Dtest.progress option to be more accurate for when the progress is written

There are several improvements to the unit test framework in this commit. * Test methods are no longer interleaved between classes. All test methods in a class are run together, with @BeforeClass and @AfterClass methods called immediately before and after the methods are run. As part of this fix, you are now required to include sequential=true in every class level @Test annotation. If you don't do this, the build will complain. * Added a TestCaseUtils.restartServer() method that will do an in core restart of the directory server during the tests. This can be used in a @BeforeClass method to ensure that the tests start with a clean directory server, and also in an @AfterClass method to cleanup after a test that makes a lot of configuration changes. So if you introduce a new test that runs fine in isolation but fails when run with other tests, you could try calling TestCaseUtils.restartServer() in its @BeforeClass method. The TestCaseUtils.restartServer() method will reinitialize the server and reload the original test configuration, but it's not quite the same as creating a completely new process. Specifically, it cannot undo any changes that were made to static member variables of a class. I've fixed a handful of places in the server where this was a problem, but there might be more lurking. If you write a test that changes static member variables of a class, please make sure that it cleans up after itself in an @AfterMethod or @AfterClass test. * The tests now use significantly much less memory. I saw a peak of only 80MB. There were two main problems. 1) TestNG holds on to all parameters and results for the whole test, and 2) since the test classes themselves live for the duration of the tests, their member variables were holding onto a lot of garbage. The in-core restart made this problem much worse because we ended up with lots of copies of the Schema, ConfigEntryS, etc. I've introduced some hacks to fix this. Basically the code uses devious methos to go in and null out the parameters and member variables after the test has run. If you're curious about the details of how we've addressed this take a look at the comments in DirectoryServerTestCase. From now on, all test classes must inherit directly or indirectly from DirectoryServerTestCase. The build will fail if they don't. * Upgrade to TestNG b5.7. There is a fix in this release that helps our tests to run in order, and I've had to make a couple of more fixes, which they will eventually put back into the trunk. * In classes with a class-level @Test annotation, TestNG treats any public method (except @Before/After* methods) as a test method. The build now points this out and asks you to either add a specific @Test annotation to the method or change the method to be non-public. I've fixed up several places where a test wasn't annotated and others where a non-test method was being treated as a test method. * The tests now report progress as they run. Run 'build testhelp' to see details on how to control the output. I've also added some new test properties, mainly to make debugging the tests easier * test.remote.debug.port: This test property allows you to remotely attach a debugger to the unit tests. If you provide a valid port value, the unit tests will not start to run until the debugger is attached. * testng.verbosity0to5: This test property controls the debugging output of TestNG. This output is useful to check the order in which test methods are invoked or other details on what TestNG is doing. Valid values are integer values from 0 (no output) to 5 (maximum output). Since this implicitly sets -Dorg.opends.test.suppressOutput=false, other stderr/stdout output generated by the unit tests will also be displayed. * org.opends.test.copyClassesToTestPackage=true: This test property copies the classes into the test server root. This enables you to run the server tools on the test server. It can slow down the test startup so the files are no longer copied by default. Thanks to Neil for trying out these changes and to him and Bo for helping me track down some of the memory leaks.

print a timestamp at the end of package so I know when I built

Fix issue 1831: dsconfig interactive mode. Overview: This change completes the dsconfig interactive mode. dsconfig now supports two levels of interactivity: 1) Usage: dsconfig A top-level menu driven text based console. Using this interactive mode the user is able able to perform multiple administrative tasks via a menu-driven interface 2) Usage: dsconfig <sub-command> dsconfig will perform the administrative task associated with the specified sub-command prompting the user for any missing information required in order to complete the task In addition, both interactive modes will prompt the user for any connection parameters not specified on the command line. Note that it is possible to run dsconfig non-interactively using the "-n" option. Although this is only available when a sub-command is provided. Other changes: 1) part of this work required implementing a generic CLI application framework. This includes an API for building and running menu-based interfaces. The classes are located in a new package called org.opends.server.util.cli 2) the dsconfig related messages have been relocated into a separate dsconfig-specific properties file.

added messages package to javadoc generation target

made rebuild target depend on generatemessages

- Restored running of messages tests to precommit target - Fixed broken SeverityTest - Added test to check for duplicate keys in messages properties files

New tests for messaging plumbing to replace old ones: - Format string cannot end with '.' (QUICKSETUP and ADMIN_TOOLS excluded) - Categories cannot span multiple files and files cannot define messages in multiple categories Addional methods for MessageDescriptorRegistry to access descriptors by defining class Corrected some offending format strings Corrected message property file boilerplates and help comments

Fix for issue 2114. The fix consists of actually adding some missing classes to quicksetup.jar (OpenDsException) and fix some code to also add the messages properties files. Only QuickSetupMessages are required, so these are the only messages that are being added.

The following modifications have the following goals: 1. Provide a fix for the CLI part of issue 1894 (consider replication in uninstall). The command line now proposes to remove references in remote servers of the server that is being uninstalled. 2. Add options to specify to uninstall only some parts of the server as appears in http://bde.central.sun.com/projects/opendsw/cmdline/commandmatrix.html. 3. Fix some bugs in the messages. 4. The fix of 1894 includes some code to display certificates to the user so that they can be viewed and accepted interactively. 5. Separate the uninstall command-line into two different command lines (uninstall-gui and uninstall) as appears in http://bde.central.sun.com/projects/opendsw/cmdline/commandmatrix.html.

added message source directories to rebuild target compilation (issue 2108)

Update package-info.java files to include the @PublicAPI annotation to indicate whether any or all of the classes in that package are intended to be part of the public API. Further, mark all classes that we intend to be part of the public API with the @PublicAPI annotation to indicate the ways in which they may be used. Note that the use of these annotations and the ultimate determination as to what is in our public API and the ways in which those elements may be used still needs to be carefully reviewed before the 1.0 release. Also, perform minor cleanup in various places througout the code. This includes: - Eliminate the use of protected fields in classes that are in the org.opends.server.api package (and the classes that extend them). The use of protected fields can be troublesome, and there are generally better ways to accomplish the same thing. - Eliminate the use of the {@inheritDoc} Javadoc tag in classes that are intended to be part of the public API. Some IDEs don't resolve {@inheritDoc} to show the actual documentation. Further, there were problems in the way that some instances of {@inheritDoc} were used, namely having a method sourced from multiple parents, and in some cases {@inheritDoc} was used to refer to code defined outside of the OpenDS codebase, which will not be properly handled by the javadoc utility. - Update a number of public API classes to mark them as final if we do not intend for them to be overridden. Further, for some classes that cannot be marked final, mark some methods final if we do not intend for those methods to be overridden.

This commit is a step toward getting OpenDS internationalized. There are still issues to be resolved before we can declare that we are internationalized but this commit covers the bulk of changes needed at this time. In general this commit converts any string values that might potentially be shown to an end user (client or administrator) to a new class called Message. This includes exception messages, error log messages, alert and email text, labels, and CLI output. Message's main interface includes methods for rendering itself as a string in the default locale using toString() or a specified locale toString(Locale). In addition to addressing localization, this would allow us to potentially support controls allowing clients to set a preferred locale for server communication or output log messages in different languages. Message extends CharSequence so it can be used in some places where strings are currently used with not code change (e.g. writing to a buffer) as well as allowing messages to be composed of one another. In order to create localized messages, instead of adding them to the *Messages.java class, you define them in the corresponding properties files. In general the property file keys are used to derive the new messages severity, category, and ordinal. There are directives that can be used in the properties file in order to avoid doing this however. For instance all the properties files used internally include the 'global.category' directive at the top of the file that instructs the generator to make all the following message belong to a single category. So for internal messages the property value key will be as follows: [SEVERITY]_[DESCRIPTION]_[ORDINAL] See the properties files themselves for more information. Once your messages are in the properties file you can use the ant target 'generatemessages' to create create MessageDescriptor objects that are referred to in the Java code. In the code you might think of these objects as replacing the int-valued message IDs. To create messages you call MessageDescriptor.get() which replaces MessageHandler.getMessage(). It might be helpful then to try to define your messages before referring to them in your code since until you run 'generatemessages' you won't have any Java-code with with to create your message objects. In order to support non-localizable text in messages (host names, DN's, etc.) Message's can be created from String values by calling Message.raw(String). In this way it is also possible to circumvent the intention of changing the APIs to use Message objects instead of Strings which is to support writing of localizable messages. This method is currently used in the code as a crutch for areas of the code that need internationalization (tagged with a 'TODO: i18n' comment). It might also be used by 3rd party developers that don't intend to localize their products. However for internal use we should not be using this method to create Messages for text that is locale sensitive. Additionally this code includes a MessageBuilder that can be used in much the same way that a StringBuilder can be used. It has a method toMessage() that can be used to generate a message object when needed. At this time this method just converts the buffer contents to a raw, unlocalizable message so this will need to addressed in the future. Some other issues: - While all of the unit tests pass after this commit, there may be issues in the code where we have no or minimal test coverage. This includes much of the setup and GUI tools packages for which I have not done any testing but will begin after this commit. - The new message related Java sources are contained in package org.opends.messages and organized in a new module src/module modeled somewhat after the admin module: src/messages/src (non-generated Java source files) src/messages/generated (generated source files) src/messages/messages (properties files for messages) If you run the code from within your IDE you will have to mark all messages/src, messages/generated and messages as source directories. - To generated the MessageDescriptor files you invoke the 'generatemessages' target. - If you run the code from within your IDE you will probably ne - This commit would change the plugin API. Here are the changes caught by DirectoryServerPluginTestCase: doShutdown(String)->doShutdown(Message) doPostDisconnect(PostDisconnectPluginResult,ClientConnection,DisconnectReason,int,String) -> doPostDisconnect(PostDisconnectPluginResult,ClientConnection,DisconnectReason,Message); - This commit aligns the entire code-base behind the new Formatter class (printf style formattings like %s) as opposed to the older MessageFormat style (using curly braces for message arguments). This allows us to provide more type safety for message arguments. So for instance you can include a %c argument specifier in your format string and the MessageDescriptor will enforce specification of a Character as message creation time. - Not all of the config framework has not been converted to use Messages. Perhaps as some point we might have a 'message' syntax for locale-sensitive textural data. I'm sure Matt will have ideas about this. - In addition to Message, MessageDescriptor and MessageBuilder, the org.opends.server.message package includes enums for Category and Severity that replace the definitions formerly found in MessageHandler. - The interface for the ErrorLogger has been simplified to allow logging of messages using a single Message parameter. The severity and category of the message will be derived from the Message itself instead of specified as arguments when a message is logged. - I will provide more documentation about this plumbing on the Wiki shortly. - I will expand on the included tests soon.