You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lécharny <el...@gmail.com> on 2012/12/22 21:06:02 UTC

[Vote] Release of ApacheDS (2.0.0-M9)

Hi,



I'd like to propose a new milestone release (2.0.0-M9) for Apache 
Directory Server.


This is a major move forward, as we have added Multi-Master replication
in this release, plus some performance improvements. 


Othewise, many other less critical bugs have been fixed.

The Configuration has been slightly modified, so a configuration from
a previous release won't work.
 
Note that it's still an intermediary version, some new milestone will be 
released before the final 2.0.0 candidate.



Here are the associated links :



ApacheDS 2.0.0-M9, revision 1425245

---------------------------------

- SVN tag r1425245: http://svn.apache.org/repos/asf/directory/apacheds/tags/2.0.0-M9/

- Nexus repository: https://repository.apache.org/content/repositories/orgapachedirectory-073/

- Distribution packages: http://people.apache.org/~elecharny



Here are the release notes for this all sub-projects:



ApacheDS 2.0.0-M9

============


    Bug

  * [DIRSERVER-1717
    <https://issues.apache.org/jira/browse/DIRSERVER-1717>] - Non
    existing AT errors ('x-read-only' and 'x-enabled') show up in the
    logs when adding new schema elements
  * [DIRSERVER-1733
    <https://issues.apache.org/jira/browse/DIRSERVER-1733>] - Cannot
    delete leaf entry -- Operation not allowed on non-leaf (66) -
    NOT_ALLOWED_ON_NON_LEAF: failed for MessageType : DEL_REQUEST
  * [DIRSERVER-1751
    <https://issues.apache.org/jira/browse/DIRSERVER-1751>] - The
    Substring index is not used during the evaluation of a search filter
  * [DIRSERVER-1752
    <https://issues.apache.org/jira/browse/DIRSERVER-1752>] - Adding a
    context entry (ads-contextentry attribute) in the configuration of a
    partition has no effect
  * [DIRSERVER-1758
    <https://issues.apache.org/jira/browse/DIRSERVER-1758>] - Error when
    setting the bad alis deref mode in replication
  * [DIRSERVER-1759
    <https://issues.apache.org/jira/browse/DIRSERVER-1759>] - The
    replReqHandler attribute is not present in the default configuration
  * [DIRSERVER-1760
    <https://issues.apache.org/jira/browse/DIRSERVER-1760>] - When one
    of the server disconnect brutally, replication stops working
  * [DIRSERVER-1762
    <https://issues.apache.org/jira/browse/DIRSERVER-1762>] - Switching
    log in debug make the service crash at startup
  * [DIRSERVER-1770
    <https://issues.apache.org/jira/browse/DIRSERVER-1770>] - Create a
    unique method to filter the AttributeTypes for the search and lookup
    rquests
  * [DIRSERVER-1776
    <https://issues.apache.org/jira/browse/DIRSERVER-1776>] - Photo and
    Jpegphoto attributes store corrupt data/Generate Syntax Errors
  * [DIRSERVER-1777
    <https://issues.apache.org/jira/browse/DIRSERVER-1777>] - Lookup
    operation done with 'name' as an attribute will not return 'cn',
    'sn', ...
  * [DIRSERVER-1782
    <https://issues.apache.org/jira/browse/DIRSERVER-1782>] - The
    various locks we are using may not be released in some case


    Improvement

  * [DIRSERVER-1721
    <https://issues.apache.org/jira/browse/DIRSERVER-1721>] -
    Replication: Two "master" servers replicate back and forth endlessly
  * [DIRSERVER-1754
    <https://issues.apache.org/jira/browse/DIRSERVER-1754>] - Add a
    default value for the context entry of the example partition in the
    configuration


    New Feature

  * [DIRSERVER-1775
    <https://issues.apache.org/jira/browse/DIRSERVER-1775>] - Add the
    EntryDN operational attribute


    Task

  * [DIRSERVER-1753
    <https://issues.apache.org/jira/browse/DIRSERVER-1753>] - Removed
    the prefNodeName=sysPrefRoot entry
  * [DIRSERVER-1781
    <https://issues.apache.org/jira/browse/DIRSERVER-1781>] - Remove the
    'list' operation from the interceptor chain


Let's vote now:

[ ] +1 | Release Apache Directory Server 2.0.0-M9

[ ] ±0 | Abstain

[ ] -1 | Do NOT release Apache Directory Server 2.0.0-M9



Thanks !




-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Antoine Levy Lambert <an...@gmx.de>.
+1 for the release

I was not able to reproduce the test error encountered by Felix. I have built with Java 6 on MacOS.

bash-3.2$ mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Maven home: /Applications/apache-maven-3.0.4
Java version: 1.6.0_37, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"

Regards,

Antoine

On Dec 23, 2012, at 3:17 PM, Felix Knecht wrote:

> I'm not sure if the failing test is a problem of mine:
> 
> [felix@www 2.0.0-M9]$ mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /etc/alternatives/mvn
> Java version: 1.7.0_07, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/jdk1.7.0_07/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.6.10-2.fc17.x86_64", arch: "amd64",
> family: "unix"
> [felix@www 2.0.0-M9]$ mvn clean install -Dintegration
> 
> ends up in following error:
> 
> Running org.apache.directory.server.operations.bind.SaslBindIT
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: No valid credentials provided (Mechanism level: Server not
> found in Kerberos database (7) - Server not found in Kerberos database)]
>        at
> com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
>        at
> org.apache.directory.ldap.client.api.LdapNetworkConnection.bindSasl(LdapNetworkConnection.java:3693)
>        at
> org.apache.directory.ldap.client.api.LdapNetworkConnection.access$200(LdapNetworkConnection.java:176)
>        at
> org.apache.directory.ldap.client.api.LdapNetworkConnection$2.run(LdapNetworkConnection.java:1463)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at javax.security.auth.Subject.doAs(Subject.java:415)
>        at
> org.apache.directory.ldap.client.api.LdapNetworkConnection.bindAsync(LdapNetworkConnection.java:1459)
>        at
> org.apache.directory.ldap.client.api.LdapNetworkConnection.bind(LdapNetworkConnection.java:1361)
>        at
> org.apache.directory.server.operations.bind.SaslBindIT.testSaslGssApiBind(SaslBindIT.java:512)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:601)
>        at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>        at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>        at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>        at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>        at
> org.apache.directory.junit.tools.MultiThreadedMultiInvoker$1$1.run(MultiThreadedMultiInvoker.java:160)
>        at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>        at java.lang.Thread.run(Thread.java:722)
> Caused by: GSSException: No valid credentials provided (Mechanism level:
> Server not found in Kerberos database (7) - Server not found in Kerberos
> database)
>        at
> sun.security.jgss.krb5.Krb5Context.initSecContext(Krb5Context.java:710)
>        at
> sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:248)
>        at
> sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179)
>        at
> com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:193)
>        ... 20 more
> Caused by: KrbException: Server not found in Kerberos database (7) -
> Server not found in Kerberos database
>        at sun.security.krb5.KrbTgsRep.<init>(KrbTgsRep.java:73)
>        at sun.security.krb5.KrbTgsReq.getReply(KrbTgsReq.java:192)
>        at sun.security.krb5.KrbTgsReq.sendAndGetCreds(KrbTgsReq.java:203)
>        at
> sun.security.krb5.internal.CredentialsUtil.serviceCreds(CredentialsUtil.java:311)
>        at
> sun.security.krb5.internal.CredentialsUtil.acquireServiceCreds(CredentialsUtil.java:115)
>        at
> sun.security.krb5.Credentials.acquireServiceCreds(Credentials.java:442)
>        at
> sun.security.jgss.krb5.Krb5Context.initSecContext(Krb5Context.java:641)
>        ... 23 more
> Caused by: KrbException: Identifier doesn't match expected value (906)
>        at sun.security.krb5.internal.KDCRep.init(KDCRep.java:143)
>        at sun.security.krb5.internal.TGSRep.init(TGSRep.java:66)
>        at sun.security.krb5.internal.TGSRep.<init>(TGSRep.java:61)
>        at sun.security.krb5.KrbTgsRep.<init>(KrbTgsRep.java:55)
>        ... 29 more
> Tests run: 17, Failures: 0, Errors: 1, Skipped: 5, Time elapsed: 14.949
> sec <<< FAILURE!
> 
> Regards
> Felix
> 
> On 12/22/2012 09:06 PM, Emmanuel Lécharny wrote:
>> Hi,
>> 
>> 
>> 
>> I'd like to propose a new milestone release (2.0.0-M9) for Apache 
>> Directory Server.
>> 
>> 
>> This is a major move forward, as we have added Multi-Master replication
>> in this release, plus some performance improvements. 
>> 
>> 
>> Othewise, many other less critical bugs have been fixed.
>> 
>> The Configuration has been slightly modified, so a configuration from
>> a previous release won't work.
>> 
>> Note that it's still an intermediary version, some new milestone will be 
>> released before the final 2.0.0 candidate.
>> 
>> 
>> 
>> Here are the associated links :
>> 
>> 
>> 
>> ApacheDS 2.0.0-M9, revision 1425245
>> 
>> ---------------------------------
>> 
>> - SVN tag r1425245: http://svn.apache.org/repos/asf/directory/apacheds/tags/2.0.0-M9/
>> 
>> - Nexus repository: https://repository.apache.org/content/repositories/orgapachedirectory-073/
>> 
>> - Distribution packages: http://people.apache.org/~elecharny
>> 
>> 
>> 
>> Here are the release notes for this all sub-projects:
>> 
>> 
>> 
>> ApacheDS 2.0.0-M9
>> 
>> ============
>> 
>> 
>>    Bug
>> 
>>  * [DIRSERVER-1717
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1717>] - Non
>>    existing AT errors ('x-read-only' and 'x-enabled') show up in the
>>    logs when adding new schema elements
>>  * [DIRSERVER-1733
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1733>] - Cannot
>>    delete leaf entry -- Operation not allowed on non-leaf (66) -
>>    NOT_ALLOWED_ON_NON_LEAF: failed for MessageType : DEL_REQUEST
>>  * [DIRSERVER-1751
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1751>] - The
>>    Substring index is not used during the evaluation of a search filter
>>  * [DIRSERVER-1752
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1752>] - Adding a
>>    context entry (ads-contextentry attribute) in the configuration of a
>>    partition has no effect
>>  * [DIRSERVER-1758
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1758>] - Error when
>>    setting the bad alis deref mode in replication
>>  * [DIRSERVER-1759
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1759>] - The
>>    replReqHandler attribute is not present in the default configuration
>>  * [DIRSERVER-1760
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1760>] - When one
>>    of the server disconnect brutally, replication stops working
>>  * [DIRSERVER-1762
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1762>] - Switching
>>    log in debug make the service crash at startup
>>  * [DIRSERVER-1770
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1770>] - Create a
>>    unique method to filter the AttributeTypes for the search and lookup
>>    rquests
>>  * [DIRSERVER-1776
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1776>] - Photo and
>>    Jpegphoto attributes store corrupt data/Generate Syntax Errors
>>  * [DIRSERVER-1777
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1777>] - Lookup
>>    operation done with 'name' as an attribute will not return 'cn',
>>    'sn', ...
>>  * [DIRSERVER-1782
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1782>] - The
>>    various locks we are using may not be released in some case
>> 
>> 
>>    Improvement
>> 
>>  * [DIRSERVER-1721
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1721>] -
>>    Replication: Two "master" servers replicate back and forth endlessly
>>  * [DIRSERVER-1754
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1754>] - Add a
>>    default value for the context entry of the example partition in the
>>    configuration
>> 
>> 
>>    New Feature
>> 
>>  * [DIRSERVER-1775
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1775>] - Add the
>>    EntryDN operational attribute
>> 
>> 
>>    Task
>> 
>>  * [DIRSERVER-1753
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1753>] - Removed
>>    the prefNodeName=sysPrefRoot entry
>>  * [DIRSERVER-1781
>>    <https://issues.apache.org/jira/browse/DIRSERVER-1781>] - Remove the
>>    'list' operation from the interceptor chain
>> 
>> 
>> Let's vote now:
>> 
>> [ ] +1 | Release Apache Directory Server 2.0.0-M9
>> 
>> [ ] ±0 | Abstain
>> 
>> [ ] -1 | Do NOT release Apache Directory Server 2.0.0-M9
>> 
>> 
>> 
>> Thanks !
>> 
>> 
>> 
>> 
> 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Emmanuel Lécharny <el...@gmail.com>.
Still waiting for a third +1...


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Pierre-Arnaud Marcelot <pa...@gmail.com>.
Hi Emmanuel,

I think you already have the three binding +1.
There's yours, Kiran's and mine.

Regards,
Pierre-Arnaud

On 27 déc. 2012, at 07:29, "Emmanuel Lécharny" <el...@gmail.com> wrote:

>
> Still waiting for a third +1...
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>

Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Felix Knecht <fe...@apache.org>.
I'm not sure if the failing test is a problem of mine:

[felix@www 2.0.0-M9]$ mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /etc/alternatives/mvn
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk1.7.0_07/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.6.10-2.fc17.x86_64", arch: "amd64",
family: "unix"
[felix@www 2.0.0-M9]$ mvn clean install -Dintegration

ends up in following error:

Running org.apache.directory.server.operations.bind.SaslBindIT
javax.security.sasl.SaslException: GSS initiate failed [Caused by
GSSException: No valid credentials provided (Mechanism level: Server not
found in Kerberos database (7) - Server not found in Kerberos database)]
        at
com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
        at
org.apache.directory.ldap.client.api.LdapNetworkConnection.bindSasl(LdapNetworkConnection.java:3693)
        at
org.apache.directory.ldap.client.api.LdapNetworkConnection.access$200(LdapNetworkConnection.java:176)
        at
org.apache.directory.ldap.client.api.LdapNetworkConnection$2.run(LdapNetworkConnection.java:1463)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:415)
        at
org.apache.directory.ldap.client.api.LdapNetworkConnection.bindAsync(LdapNetworkConnection.java:1459)
        at
org.apache.directory.ldap.client.api.LdapNetworkConnection.bind(LdapNetworkConnection.java:1361)
        at
org.apache.directory.server.operations.bind.SaslBindIT.testSaslGssApiBind(SaslBindIT.java:512)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
        at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
        at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at
org.apache.directory.junit.tools.MultiThreadedMultiInvoker$1$1.run(MultiThreadedMultiInvoker.java:160)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)
Caused by: GSSException: No valid credentials provided (Mechanism level:
Server not found in Kerberos database (7) - Server not found in Kerberos
database)
        at
sun.security.jgss.krb5.Krb5Context.initSecContext(Krb5Context.java:710)
        at
sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:248)
        at
sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179)
        at
com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:193)
        ... 20 more
Caused by: KrbException: Server not found in Kerberos database (7) -
Server not found in Kerberos database
        at sun.security.krb5.KrbTgsRep.<init>(KrbTgsRep.java:73)
        at sun.security.krb5.KrbTgsReq.getReply(KrbTgsReq.java:192)
        at sun.security.krb5.KrbTgsReq.sendAndGetCreds(KrbTgsReq.java:203)
        at
sun.security.krb5.internal.CredentialsUtil.serviceCreds(CredentialsUtil.java:311)
        at
sun.security.krb5.internal.CredentialsUtil.acquireServiceCreds(CredentialsUtil.java:115)
        at
sun.security.krb5.Credentials.acquireServiceCreds(Credentials.java:442)
        at
sun.security.jgss.krb5.Krb5Context.initSecContext(Krb5Context.java:641)
        ... 23 more
Caused by: KrbException: Identifier doesn't match expected value (906)
        at sun.security.krb5.internal.KDCRep.init(KDCRep.java:143)
        at sun.security.krb5.internal.TGSRep.init(TGSRep.java:66)
        at sun.security.krb5.internal.TGSRep.<init>(TGSRep.java:61)
        at sun.security.krb5.KrbTgsRep.<init>(KrbTgsRep.java:55)
        ... 29 more
Tests run: 17, Failures: 0, Errors: 1, Skipped: 5, Time elapsed: 14.949
sec <<< FAILURE!

Regards
Felix

On 12/22/2012 09:06 PM, Emmanuel Lécharny wrote:
> Hi,
> 
> 
> 
> I'd like to propose a new milestone release (2.0.0-M9) for Apache 
> Directory Server.
> 
> 
> This is a major move forward, as we have added Multi-Master replication
> in this release, plus some performance improvements. 
> 
> 
> Othewise, many other less critical bugs have been fixed.
> 
> The Configuration has been slightly modified, so a configuration from
> a previous release won't work.
>  
> Note that it's still an intermediary version, some new milestone will be 
> released before the final 2.0.0 candidate.
> 
> 
> 
> Here are the associated links :
> 
> 
> 
> ApacheDS 2.0.0-M9, revision 1425245
> 
> ---------------------------------
> 
> - SVN tag r1425245: http://svn.apache.org/repos/asf/directory/apacheds/tags/2.0.0-M9/
> 
> - Nexus repository: https://repository.apache.org/content/repositories/orgapachedirectory-073/
> 
> - Distribution packages: http://people.apache.org/~elecharny
> 
> 
> 
> Here are the release notes for this all sub-projects:
> 
> 
> 
> ApacheDS 2.0.0-M9
> 
> ============
> 
> 
>     Bug
> 
>   * [DIRSERVER-1717
>     <https://issues.apache.org/jira/browse/DIRSERVER-1717>] - Non
>     existing AT errors ('x-read-only' and 'x-enabled') show up in the
>     logs when adding new schema elements
>   * [DIRSERVER-1733
>     <https://issues.apache.org/jira/browse/DIRSERVER-1733>] - Cannot
>     delete leaf entry -- Operation not allowed on non-leaf (66) -
>     NOT_ALLOWED_ON_NON_LEAF: failed for MessageType : DEL_REQUEST
>   * [DIRSERVER-1751
>     <https://issues.apache.org/jira/browse/DIRSERVER-1751>] - The
>     Substring index is not used during the evaluation of a search filter
>   * [DIRSERVER-1752
>     <https://issues.apache.org/jira/browse/DIRSERVER-1752>] - Adding a
>     context entry (ads-contextentry attribute) in the configuration of a
>     partition has no effect
>   * [DIRSERVER-1758
>     <https://issues.apache.org/jira/browse/DIRSERVER-1758>] - Error when
>     setting the bad alis deref mode in replication
>   * [DIRSERVER-1759
>     <https://issues.apache.org/jira/browse/DIRSERVER-1759>] - The
>     replReqHandler attribute is not present in the default configuration
>   * [DIRSERVER-1760
>     <https://issues.apache.org/jira/browse/DIRSERVER-1760>] - When one
>     of the server disconnect brutally, replication stops working
>   * [DIRSERVER-1762
>     <https://issues.apache.org/jira/browse/DIRSERVER-1762>] - Switching
>     log in debug make the service crash at startup
>   * [DIRSERVER-1770
>     <https://issues.apache.org/jira/browse/DIRSERVER-1770>] - Create a
>     unique method to filter the AttributeTypes for the search and lookup
>     rquests
>   * [DIRSERVER-1776
>     <https://issues.apache.org/jira/browse/DIRSERVER-1776>] - Photo and
>     Jpegphoto attributes store corrupt data/Generate Syntax Errors
>   * [DIRSERVER-1777
>     <https://issues.apache.org/jira/browse/DIRSERVER-1777>] - Lookup
>     operation done with 'name' as an attribute will not return 'cn',
>     'sn', ...
>   * [DIRSERVER-1782
>     <https://issues.apache.org/jira/browse/DIRSERVER-1782>] - The
>     various locks we are using may not be released in some case
> 
> 
>     Improvement
> 
>   * [DIRSERVER-1721
>     <https://issues.apache.org/jira/browse/DIRSERVER-1721>] -
>     Replication: Two "master" servers replicate back and forth endlessly
>   * [DIRSERVER-1754
>     <https://issues.apache.org/jira/browse/DIRSERVER-1754>] - Add a
>     default value for the context entry of the example partition in the
>     configuration
> 
> 
>     New Feature
> 
>   * [DIRSERVER-1775
>     <https://issues.apache.org/jira/browse/DIRSERVER-1775>] - Add the
>     EntryDN operational attribute
> 
> 
>     Task
> 
>   * [DIRSERVER-1753
>     <https://issues.apache.org/jira/browse/DIRSERVER-1753>] - Removed
>     the prefNodeName=sysPrefRoot entry
>   * [DIRSERVER-1781
>     <https://issues.apache.org/jira/browse/DIRSERVER-1781>] - Remove the
>     'list' operation from the interceptor chain
> 
> 
> Let's vote now:
> 
> [ ] +1 | Release Apache Directory Server 2.0.0-M9
> 
> [ ] ±0 | Abstain
> 
> [ ] -1 | Do NOT release Apache Directory Server 2.0.0-M9
> 
> 
> 
> Thanks !
> 
> 
> 
> 


Result [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Emmanuel Lécharny <el...@gmail.com>.
The ApacheDS 2.0.0-M9 release vote has passed with 3 binding +1 and one
non-binding +1 vote

Binding :

Emmanuel
Kiran
Pierre-Arnaud

Non binding :
Antoine

Thanks !


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Result [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Emmanuel Lécharny <el...@gmail.com>.
The ApacheDS 2.0.0-M9 release vote has passed with 3 binding +1 and one
non-binding +1 vote

Bindings :

Emmanuel
Kiran
Pierre-Arnaud

Non binding :
Antoine

Thanks !


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Emmanuel Lécharny <el...@gmail.com>.
Thanks Pierre-Arnaud.

At some point, we will need to add a page on the site to explain how to
check a release...

But first, we need to get the new site out 

Le 12/23/12 9:11 AM, Pierre-Arnaud Marcelot a écrit :
> You can also configure Maven in your settings.xml file (~/.m2/settings.xml) to use the Nexus repository built for the release.
> Here's how I generated the installers for Emmanuel:
>>     <profile>
>>       <id>apacheds-nexus</id>
>>       <repositories>
>>         <repository>
>>           <id>apacheds-nexus</id>
>>           <name>ApacheDS Nexus</name>
>>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-073/</url>
>>           <layout>default</layout>
>>         </repository>
>>       </repositories>
>>       <pluginRepositories>
>>         <pluginRepository>
>>           <id>apacheds-nexus</id>
>>           <name>ApacheDS Nexus</name>
>>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-073/</url>
>>           <layout>default</layout>
>>         </pluginRepository>
>>       </pluginRepositories>
>>     </profile>
>
> For LDAP API, it would be:
>>     <profile>
>>       <id>api-nexus</id>
>>       <repositories>
>>         <repository>
>>           <id>api-nexus</id>
>>           <name>LDAP API Nexus</name>
>>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-068/</url>
>>           <layout>default</layout>
>>         </repository>
>>       </repositories>
>>       <pluginRepositories>
>>         <pluginRepository>
>>           <id>api-nexus</id>
>>           <name>LDAPI API Nexus</name>
>>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-068/</url>
>>           <layout>default</layout>
>>         </pluginRepository>
>>       </pluginRepositories>
>>     </profile>
> Off course, specify the name of the profile in the command line or add it by default in the settings.xml:
>>   <activeProfiles>
>>     <activeProfile> api-nexus</activeProfile>
>>   </activeProfiles>
>
> Hope this helps,
> Pierre-Arnaud
>
> On 23 déc. 2012, at 08:29, Emmanuel Lécharny <el...@gmail.com> wrote:
>
>> Le 12/23/12 4:28 AM, Kiran Ayyagari a écrit :
>>> failed to build from the source cause the apacheds/pom.xml refers to
>>> API/shared version 1.0.0-M14 instead of 1.0.0-M13
>> Ah, you have to build LDAP API M14 before building ApacheDS
>>
>> -- 
>> Regards,
>> Cordialement,
>> Emmanuel Lécharny
>> www.iktek.com 
>>


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
You can also configure Maven in your settings.xml file (~/.m2/settings.xml) to use the Nexus repository built for the release.
Here's how I generated the installers for Emmanuel:
>     <profile>
>       <id>apacheds-nexus</id>
>       <repositories>
>         <repository>
>           <id>apacheds-nexus</id>
>           <name>ApacheDS Nexus</name>
>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-073/</url>
>           <layout>default</layout>
>         </repository>
>       </repositories>
>       <pluginRepositories>
>         <pluginRepository>
>           <id>apacheds-nexus</id>
>           <name>ApacheDS Nexus</name>
>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-073/</url>
>           <layout>default</layout>
>         </pluginRepository>
>       </pluginRepositories>
>     </profile>


For LDAP API, it would be:
>     <profile>
>       <id>api-nexus</id>
>       <repositories>
>         <repository>
>           <id>api-nexus</id>
>           <name>LDAP API Nexus</name>
>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-068/</url>
>           <layout>default</layout>
>         </repository>
>       </repositories>
>       <pluginRepositories>
>         <pluginRepository>
>           <id>api-nexus</id>
>           <name>LDAPI API Nexus</name>
>           <url>https://repository.apache.org/content/repositories/orgapachedirectory-068/</url>
>           <layout>default</layout>
>         </pluginRepository>
>       </pluginRepositories>
>     </profile>

Off course, specify the name of the profile in the command line or add it by default in the settings.xml:
>   <activeProfiles>
>     <activeProfile> api-nexus</activeProfile>
>   </activeProfiles>


Hope this helps,
Pierre-Arnaud

On 23 déc. 2012, at 08:29, Emmanuel Lécharny <el...@gmail.com> wrote:

> Le 12/23/12 4:28 AM, Kiran Ayyagari a écrit :
>> failed to build from the source cause the apacheds/pom.xml refers to
>> API/shared version 1.0.0-M14 instead of 1.0.0-M13
> 
> Ah, you have to build LDAP API M14 before building ApacheDS
> 
> -- 
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com 
> 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Kiran Ayyagari <ka...@apache.org>.
On Sun, Dec 23, 2012 at 12:59 PM, Emmanuel Lécharny <el...@gmail.com>wrote:

> Le 12/23/12 4:28 AM, Kiran Ayyagari a écrit :
> > failed to build from the source cause the apacheds/pom.xml refers to
> > API/shared version 1.0.0-M14 instead of 1.0.0-M13
>
> Ah, you have to build LDAP API M14 before building ApacheDS
>
> I checked out M13 based on the URL in LDAP api release mail :)

otoh, I have encountered a compilation error in
DirectoryServiceAnnotationTest of core-annotations
when compiled with 1.6.0_26 but I don't consider this as a blocker cause
JDK6 has reached its EOL
and this error doesn't show up while using JDK 7 (Emmanuel has already
fixed this problem in trunk)


[X] +1 | Release Apache Directory Server 2.0.0-M9

thanks everyone

 --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
>


-- 
Kiran Ayyagari
http://keydap.com

Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 12/23/12 4:28 AM, Kiran Ayyagari a écrit :
> failed to build from the source cause the apacheds/pom.xml refers to
> API/shared version 1.0.0-M14 instead of 1.0.0-M13

Ah, you have to build LDAP API M14 before building ApacheDS

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 12/23/12 4:28 AM, Kiran Ayyagari a écrit :
> failed to build from the source cause the apacheds/pom.xml refers to
> API/shared version 1.0.0-M14 instead of 1.0.0-M13
Damn ! Let me fix that ...


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Re: [Vote] Release of ApacheDS (2.0.0-M9)

Posted by Kiran Ayyagari <ka...@apache.org>.
failed to build from the source cause the apacheds/pom.xml refers to
API/shared version 1.0.0-M14 instead of 1.0.0-M13

On Sun, Dec 23, 2012 at 1:36 AM, Emmanuel Lécharny <el...@gmail.com>wrote:

> Hi,
>
>
>
> I'd like to propose a new milestone release (2.0.0-M9) for Apache
> Directory Server.
>
>
> This is a major move forward, as we have added Multi-Master replication
> in this release, plus some performance improvements.
>
>
> Othewise, many other less critical bugs have been fixed.
>
> The Configuration has been slightly modified, so a configuration from
> a previous release won't work.
>
> Note that it's still an intermediary version, some new milestone will be
> released before the final 2.0.0 candidate.
>
>
>
> Here are the associated links :
>
>
>
> ApacheDS 2.0.0-M9, revision 1425245
>
> ---------------------------------
>
> - SVN tag r1425245:
> http://svn.apache.org/repos/asf/directory/apacheds/tags/2.0.0-M9/
>
> - Nexus repository:
> https://repository.apache.org/content/repositories/orgapachedirectory-073/
>
> - Distribution packages: http://people.apache.org/~elecharny
>
>
>
> Here are the release notes for this all sub-projects:
>
>
>
> ApacheDS 2.0.0-M9
>
> ============
>
>
>     Bug
>
>   * [DIRSERVER-1717
>     <https://issues.apache.org/jira/browse/DIRSERVER-1717>] - Non
>     existing AT errors ('x-read-only' and 'x-enabled') show up in the
>     logs when adding new schema elements
>   * [DIRSERVER-1733
>     <https://issues.apache.org/jira/browse/DIRSERVER-1733>] - Cannot
>     delete leaf entry -- Operation not allowed on non-leaf (66) -
>     NOT_ALLOWED_ON_NON_LEAF: failed for MessageType : DEL_REQUEST
>   * [DIRSERVER-1751
>     <https://issues.apache.org/jira/browse/DIRSERVER-1751>] - The
>     Substring index is not used during the evaluation of a search filter
>   * [DIRSERVER-1752
>     <https://issues.apache.org/jira/browse/DIRSERVER-1752>] - Adding a
>     context entry (ads-contextentry attribute) in the configuration of a
>     partition has no effect
>   * [DIRSERVER-1758
>     <https://issues.apache.org/jira/browse/DIRSERVER-1758>] - Error when
>     setting the bad alis deref mode in replication
>   * [DIRSERVER-1759
>     <https://issues.apache.org/jira/browse/DIRSERVER-1759>] - The
>     replReqHandler attribute is not present in the default configuration
>   * [DIRSERVER-1760
>     <https://issues.apache.org/jira/browse/DIRSERVER-1760>] - When one
>     of the server disconnect brutally, replication stops working
>   * [DIRSERVER-1762
>     <https://issues.apache.org/jira/browse/DIRSERVER-1762>] - Switching
>     log in debug make the service crash at startup
>   * [DIRSERVER-1770
>     <https://issues.apache.org/jira/browse/DIRSERVER-1770>] - Create a
>     unique method to filter the AttributeTypes for the search and lookup
>     rquests
>   * [DIRSERVER-1776
>     <https://issues.apache.org/jira/browse/DIRSERVER-1776>] - Photo and
>     Jpegphoto attributes store corrupt data/Generate Syntax Errors
>   * [DIRSERVER-1777
>     <https://issues.apache.org/jira/browse/DIRSERVER-1777>] - Lookup
>     operation done with 'name' as an attribute will not return 'cn',
>     'sn', ...
>   * [DIRSERVER-1782
>     <https://issues.apache.org/jira/browse/DIRSERVER-1782>] - The
>     various locks we are using may not be released in some case
>
>
>     Improvement
>
>   * [DIRSERVER-1721
>     <https://issues.apache.org/jira/browse/DIRSERVER-1721>] -
>     Replication: Two "master" servers replicate back and forth endlessly
>   * [DIRSERVER-1754
>     <https://issues.apache.org/jira/browse/DIRSERVER-1754>] - Add a
>     default value for the context entry of the example partition in the
>     configuration
>
>
>     New Feature
>
>   * [DIRSERVER-1775
>     <https://issues.apache.org/jira/browse/DIRSERVER-1775>] - Add the
>     EntryDN operational attribute
>
>
>     Task
>
>   * [DIRSERVER-1753
>     <https://issues.apache.org/jira/browse/DIRSERVER-1753>] - Removed
>     the prefNodeName=sysPrefRoot entry
>   * [DIRSERVER-1781
>     <https://issues.apache.org/jira/browse/DIRSERVER-1781>] - Remove the
>     'list' operation from the interceptor chain
>
>
> Let's vote now:
>
> [ ] +1 | Release Apache Directory Server 2.0.0-M9
>
> [ ] ±0 | Abstain
>
> [ ] -1 | Do NOT release Apache Directory Server 2.0.0-M9
>
>
>
> Thanks !
>
>
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
>


-- 
Kiran Ayyagari
http://keydap.com