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

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.

Remove the dependence on AspectJ for all non method-entry and method-exit related debug messages. All debug statements will now work w/o weaving enabled. However, method-entry and method-exit debug messages work only with weaving enabled.

Fixed spelling error of a debug method (org.opends.server.loggers.debug.DebugLogger.debugCought should be debugCaught).

Remove blank lines at the beginning of methods left after eliminating the debugEnter and debugConstructor calls.

Update all CDDL headers in source files to remove a typo.

This removes old debug logging framework method calls that are going to be automatically instrumented by AspectJ. Non instrumented debug method calls are updated to use the new debug framework methods. However, the new debug logging framework is not yet active as the Aspects are not weaved in. After this revision, debug logging will be disabled in the server until the new AOP framework is complete. - Removed debugEnter and debugConstructor from all source files. - Removed CLASS_NAME static string for debug purposes. - Removed old debug logging framework. - Added new debug logging frameworking using AOP. - Added AspectJ binary and libraries. - Change all modified files copyrights to include 2007.

Make several changes to administrative shell scripts provided with OpenDS. All of these changes fall under the blanket of issue 882, but are also associated with a number of individual sub-issues. The changes include: - Create new "_client-script.sh" and "_server-script.sh" shell scripts that hold the majority of the logic required to launch the client-side and server-side tools (Issue #873). - Explicitly set the PATH, LD_LIBRARY_PATH, and LD_PRELOAD (and the 32-bit and 64-bit specific variants of LD_LIBRARY_PATH and LD_PRELOAD) to ensure better security and more consistent behavior when invoking external commands (Issue #607). - Fix potential problems that could arise if either OpenDS or the Java runtime are installed in a path that contains spaces (Issue #820). - Update the start-ds.sh script so that it always creates a PID file, whether running in the foreground or in the background (Issue #859). - Update the start-ds.sh script so that when running in the background it will not exit until it confirms that the server is actually running. It will also display any messages written to standard output/standard error during startup (Issue #590). - Update the stop-ds.sh script so that it can either perform a local stop (via kill with the TERM signal) or a remote stop (over LDAP using the shutdown task). If the script is invoked with no arguments and there is a local PID file present, then it will be a local stop via kill, and it will wait until the server actually has stopped before exiting. Otherwise it will be a remote stop over LDAP (Issue #871).