org.forgerock / org.forgerock.opendj

15 Jul, 2014

1 commit

13 Dec, 2013

1 commit

  • 08290ad6   OPENDJ-1222 Global update of CDDL copyright headers ... Browse Dir » 
    
Most of the replace was done by global search replace from Eclipse via regular expressions.
Individual files had incorrect headers or badly formatted ones, so some of them have been done manually by replacing the content between CDDL HEADER START and CDDL HEADER END.
Some headers were quoting "trunk/opends/resource/legal-notices/CDDLv1_0.txt" while it should have been "legal-notices/CDDLv1_0.txt".


Removed:
- resource/legal-notices/OpenDS.LICENSE

The following required manual changes:
- build.xml
- ext/checkstyle/opendj.sourceheader
- resource/admin/java-utilities.xsl
- src/build-tools/org/opends/build/tools/ProcessFilesForPackages.java
- src/build-tools/windows/*
- src/pkg/opends-dsml-gateway_proto.py
- src/pkg/opends_proto.py
- src/server/org/opends/server/util/ServerConstants.java
- tests/staf-tests/functional-tests/shared/data/aci/aci_targattrfilter/add_aci18.ldif
- tests/staf-tests/build.bat

An incorrect header mentionning "exclude" instead of "include" in the copyright header existed for: tests/staf-tests/functional-tests/testcases/backends/backup/**/*

Some files have no copyright headers at all. I did not update them. Here is some of them (more exist):
- tests/staf-tests/functional-tests/shared/data/core/psearch/**/*.ref
- tests/staf-tests/functional-tests/shared/data/core/psearch/**/delete.ldif


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

05 Jun, 2013

1 commit

20 Feb, 2013

1 commit

07 Aug, 2012

1 commit

09 Nov, 2011

1 commit

28 Sep, 2011

1 commit

18 Aug, 2011

1 commit

13 Jul, 2011

1 commit

24 Jun, 2011

2 commits

23 Jun, 2011

1 commit

18 Aug, 2010

1 commit

  • dbedb655   Cleanup. Remove references to Java 5 since we no longer support it. ... Browse Dir » 
    Cleanup messages, removing unnecessary casts (due to bugs in early versions of Java 5), removing dead code.
The minimal version has been set to Java 1.6.0_10.
Also cleanup the Java Stubs for MacOS, removed the StatusPanel (replaced by ControlPanel since 1.2), and update Info.plist to require 1.6 or higher, show 2.3 as version.



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

31 May, 2010

1 commit

29 Apr, 2010

1 commit

14 Jan, 2010

1 commit

04 Jan, 2010

1 commit

10 Nov, 2009

1 commit

02 Feb, 2009

1 commit

31 Jan, 2009

1 commit

06 Jan, 2009

1 commit

18 Dec, 2008

1 commit

26 May, 2008

1 commit

  • bf8d765c   Fix for 3259: No messages support in example plugin ... Browse Dir » 
    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)


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

18 Mar, 2008

1 commit

06 Mar, 2008

1 commit

27 Feb, 2008

1 commit

  • 069eb677   For Configuration Reference generated doc: ... Browse Dir » 
    Added 2 new parameters (java properties) for M1 needs (1st one only):

OpendsWiki - The URL of the OpenDS Wiki
             (default is "https://www.opends.org/wiki")
OpendsHome - The URL of the OpenDS project Home page
             (default is "http://www.opends.org")

Usage:
In the M1 build target, add :
      <jvmarg value="-DOpendsWiki=https://www.opends.org/<M1 Wiki>"/>
 
Note that as a side effect, now all the html files are generated (index.html and maintop.html were not generated until now)





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

12 Feb, 2008

2 commits

08 Feb, 2008

2 commits

17 Jan, 2008

1 commit

14 Jan, 2008

2 commits

  • dd793810   Add support to admin framework for retrieving an i18n description of the constra… ... Browse Dir » 
    …ints applicable to an aggregation property. This is required for issue 2004 (HTML configuration guide generation).

Two new methods are added to the AggregationPropertyDefinition: getSourceConstraintSynopsis() and getSourceConstraintSynopsis(Locale). All aggregation definitions which had constraints have been updated to included the description. In addition, dsconfig is modified to output the constraint description when displaying verbose help on aggregation properties.

git-svn-id: https://svn.forgerock.org/opendj/trunk@3669 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 5bd2e865   Partial fix for issue 2661 - public APIs must not reference private classes. ... Browse Dir » 
    In org.opends.server.admin.Configuration replace

  ManagedObjectDefinition<...,...> definition()

With:

  Class<? extends Configuration> configurationClass()

And remove method:

  ServerManagedObject<...> managedObject()

This decouples generated server-side management APIs from the rest of the framework with the exception of configuration listeners.


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

19 Dec, 2007

2 commits

  • 20353bca   Fix issue 2451 part #1: https://opends.dev.java.net/issues/show_bug.cgi?id=2451 ... Browse Dir » 
    It is now possible to override the default naming argument for dsconfig sub-commands using the CLI profile in the XML definitions. To do this add the "naming-argument-override" attribute to a relation's CLI profile relation element. For example:

 <adm:relation name="virtual-attribute">
   <adm:one-to-many />
   <adm:profile name="ldap">
     <ldap:rdn-sequence>
       cn=Virtual Attributes,cn=config
     </ldap:rdn-sequence>
   </adm:profile>
   <adm:profile name="cli">
     <cli:relation naming-argument-override="name">
       <cli:default-property name="enabled" />
       <cli:default-property name="attribute-type" />
     </cli:relation>
   </adm:profile>
 </adm:relation>


git-svn-id: https://svn.forgerock.org/opendj/trunk@3591 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 8559dade   Fix for issue 2446 part #1. ... Browse Dir » 
    Add support to the admin framework for specifying one or more "default" managed objects which should be created automatically when a parent managed object is created. The XML mark-up is provided as part of the parent managed object's relation definition as follows (the sample is taken from the LocalDBBackend XML definition):

     <adm:relation name="local-db-index">
       <adm:one-to-many naming-property="attribute">

         <adm:default-managed-object name="aci">
           <adm:property name="index-type">
             <adm:value>presence</adm:value>
           </adm:property>
           <adm:property name="attribute">
             <adm:value>aci</adm:value>
           </adm:property>
         </adm:default-managed-object>

         <adm:default-managed-object name="entryUUID">
           <adm:property name="index-type">
             <adm:value>equality</adm:value>
           </adm:property>
           <adm:property name="attribute">
             <adm:value>entryUUID</adm:value>
           </adm:property>
         </adm:default-managed-object>

         <adm:default-managed-object name="objectClass">
           <adm:property name="index-type">
             <adm:value>equality</adm:value>
           </adm:property>
           <adm:property name="attribute">
             <adm:value>objectClass</adm:value>
           </adm:property>
         </adm:default-managed-object>
       </adm:one-to-many>

The functionality is implemented on the client-side API in a generic manner so that it is independent of the underlying driver implementation (so the default indexes would be created if we had an offline direct to file driver as well).



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

16 Nov, 2007

2 commits

  • 5fa5763c   Update admin framework and dsconfig to support tagging ... Browse Dir » 
    of component definitions as advanced and customizable:

* advanced components: these will not be displayed by
  default in dsconfig. Examples include the various
  system backends

* customizable components: these components are tagged
  as intended for customization using the CLI XML
  profile. Customizable components are usually the top
  level components previously referred to as "generic"
  by dsconfig. This term confused users who would, for
  example, mistake a "generic" backend for a JE backend.

This change is part of issue 1829.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3460 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • b3106d3b   Advanced properties phase 1: tag advanced properties and perform ... Browse Dir » 
    various clean-up to the XML definitions:

   * clean up typos and any bad grammar in the synopsis/description
     elements

   * fixed common errors. For example, there were many places where the
     synopsis was repeated in the description (the description is only
     ever used in conjunction with the synopsis). There were also many
     places where the <adm:user-friendly-name> was being used in
     property definition description elements to refer to the property
     name, when it actually refers to the managed object name

   * split big synopsis (not sure of the plural form - synopsi?) where
     possible - there were lots of cases where we'd have a big synopsis
     but no description

   * overrode properties with sensible default values where
     appropriate (for example, I provided sensible default values for
     some of the attribute-type properties in the virtual attribute
     definitions)

   * generally made documentation more consistent across the definitions

   * removed unneeded XML attributes of the form 'mandatory="false"'.
     Attributes only need to be specified if their value is true as
     they default to false. Adding redundant attributes just makes the
     XML harder to read

   * removed any documentation that referred to the configuration in
     LDAP related terms (with one exception in the Schema backend). All
     documentation now refers to other properties using the property
     names, not their associated LDAP attribute.


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

28 Sep, 2007

1 commit

27 Sep, 2007

1 commit

  • c40a66ed   Improvements to aggregation support and foundation work for expressing arbitrary… ... Browse Dir » 
    … constraints within components.

This change adds support for defining arbitrary conditions which can be used to test properties and their values. Conditions can be used within aggregations to define 1) when a referenced managed object needs enabling and 2) when it is enabled. For example, the LDAP connection handler requires that its key manager provider and trust manager provider are enabled when it is enable and when either SSL or StartTLS are enabled.

Conditions are also intended for use within the existing constraint/dependency support. For example, it should be possible to indicate that a property "min" is always less than or equal to a property "max", or that when "use-ssl" is set to true, any required SSL configuration related properties are also defined. This will be implemented in a subsequent change (this change just focuses on the work required to resolve issue 1449).

This change adds support for the following conditions:

* logical "not"
* logical "and"
* logical "or"
* logical "implies"
* contains - determines if a property contains a particular value
* is-present - determines if a property has any values (incl. defaults)

More will be added as required.


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

26 Sep, 2007

1 commit