Hi Emmanuel, We have a bunch of test failures in Directory Server when I updated it locally to use 2.1.9:
[ERROR] Failures: [ERROR] SimpleBindJndiIT.testSimpleBindAPrincipalNullPassword:331 Unexpected exception type thrown, expected: <org.apache.directory.api.ldap.model.exception.LdapUnwillingToPerformException> but was: <org.apache.directory.api.ldap.model.exception.LdapAuthenticationException> [ERROR] SimpleBindIT.testSimpleBindAPrincipalNoPassword:204 Unexpected exception type thrown, expected: <org.apache.directory.api.ldap.model.exception.LdapUnwillingToPerformException> but was: <org.apache.directory.api.ldap.model.exception.LdapAuthenticationException> [ERROR] SimpleBindIT.testSimpleBindAPrincipalNullPassword:219 Unexpected exception type thrown, expected: <org.apache.directory.api.ldap.model.exception.LdapUnwillingToPerformException> but was: <org.apache.directory.api.ldap.model.exception.LdapAuthenticationException> [ERROR] Errors: [ERROR] MetaComparatorHandlerIT.testAddComparatorWithByteCodeToDisabledSchema:262 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.comparators.DummyComparator' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] MetaComparatorHandlerIT.testAddComparatorWithByteCodeToEnabledSchema:220 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.comparators.DummyComparator' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] MetaNormalizerHandlerIT.testAddNormalizerWithByteCodeToDisabledSchema:223 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.normalizers.DummyNormalizer' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] MetaNormalizerHandlerIT.testAddNormalizerWithByteCodeToEnabledSchema:188 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.normalizers.DummyNormalizer' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] MetaSyntaxCheckerHandlerIT.testAddSyntaxCheckerWithByteCodeOnDisabledSchema:219 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.syntaxCheckers.DummySyntaxChecker' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] MetaSyntaxCheckerHandlerIT.testAddSyntaxCheckerWithByteCodeOnEnabledSchema:184 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.syntaxCheckers.DummySyntaxChecker' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] SubschemaSubentryIT.testAddRemoveReplaceComparators:522->modify:1985 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.comparators.DummyComparator' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] SubschemaSubentryIT.testAddRemoveReplaceNormalizers:670->modify:1985 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.normalizers.DummyNormalizer' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [ERROR] SubschemaSubentryIT.testAddRemoveReplaceSyntaxCheckers:368->modify:1985 » LdapUnwillingToPerform ERR_16081_WONT_LOAD_CLASS Refusing to load class 'org.apache.directory.api.ldap.model.schema.syntaxCheckers.DummySyntaxChecker' from the m-bytecode attribute : loading schema element implementations from entry-provided bytecode is disabled by default, as the bytecode may originate from an untrusted LDAP peer. Set the 'org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading' system property to true to explicitly enable it. [INFO] [ERROR] Tests run: 763, Failures: 3, Errors: 9, Skipped: 171 Colm. On Thu, Oct 1, 2026 at 8:56 PM Emmanuel Lécharny <[email protected]> wrote: > > Hi Colm, > > LDAP API 2.1.9 j-has just been released a couple of days ago. > > ApacheDS is soon to be released, but I have a SASL test failing that I > need to fix. > > I'm also working on releasing Studio, with a few tests failing. > > On 30/09/2026 16:39, Colm O hEigeartaigh wrote: > > Hi Emmanuel, > > > > Where do we stand in general with Apache DS + the new LDAP API release? > > > > Colm. > > > > On Wed, Sep 30, 2026 at 3:35 PM Emmanuel Lecharny <[email protected]> > > wrote: > >> > >> Hi Gary, > >> > >> the current trunk refers to parent pom 51, not 51-SNAPSHOT. Actually, we > >> should move it to 52, but it's not urgent. > >> > >> > >> May be it's just a matter of running a mvn deploy on apacheds? > >> > >> On 9/30/26 14:38, Gary D. Gregory wrote: > >>> Hi All, > >>> > >>> I need to test locally the current snapshot to see if it would fix a > >>> problem I have. > >>> When I try to bump from 2.0.0.AM27 to 2.0.0.AM28-SNAPSHOT, I get: > >>> > >>> ERROR] Failed to read artifact descriptor for > >>> org.apache.directory.server:apacheds-core:jar:2.0.0.AM28-SNAPSHOT > >>> [ERROR] Caused by: The following artifacts could not be resolved: > >>> org.apache.directory.project:project:pom:51-SNAPSHOT (absent): Could not > >>> find artifact org.apache.directory.project:project:pom:51-SNAPSHOT in > >>> jfrog-artifactory (https://redacted/artifactory/remote-maven-repo1-ams) > >>> [ERROR] Failed to read artifact descriptor for > >>> org.apache.directory.server:apacheds-core-integ:jar:2.0.0.AM28-SNAPSHOT > >>> [ERROR] Caused by: The following artifacts could not be resolved: > >>> org.apache.directory.project:project:pom:51-SNAPSHOT (absent): > >>> org.apache.directory.project:project:pom:51-SNAPSHOT was not found in > >>> https://redacted/artifactory/remote-maven-repo1-ams during a previous > >>> attempt. This failure was cached in the local repository and resolution > >>> is not reattempted until the update interval of jfrog-artifactory has > >>> elapsed or updates are forced > >>> [ERROR] Failed to read artifact descriptor for > >>> org.apache.directory.server:apacheds-test-framework:jar:2.0.0.AM28-SNAPSHOT > >>> [ERROR] Caused by: The following artifacts could not be resolved: > >>> org.apache.directory.project:project:pom:51-SNAPSHOT (absent): > >>> org.apache.directory.project:project:pom:51-SNAPSHOT was not found in > >>> https://redacted/artifactory/remote-maven-repo1-ams during a previous > >>> attempt. This failure was cached in the local repository and resolution > >>> is not reattempted until the update interval of jfrog-artifactory has > >>> elapsed or updates are forced > >>> > >>> Would you please the current state of 2.0.0.AM28-SNAPSHOT? > >>> > >>> Thank you! > >>> Gary > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > -- > ------------------------ > Emmanuel Lécharny > [email protected] > [email protected] > ------------------------ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
