Ok, fixed, I thing. There was a missing import on org.apache.directory.api.ldap.model.filter.ExprNode in apacheds-core.

It has been committed, and tests are passing ok for Java 8, 11 and 12 on linux now. Waiting for Java 8 on windows. (see https://builds.apache.org/blue/organizations/jenkins/dir-server-pipeline/detail/dir-server-pipeline/202/pipeline/40)

Weird enough, those tests never failed on my computer...

On 26/03/2020 10:45, Colm O hEigeartaigh wrote:
I don't see anything obvious, printing out the stacktrace I see:


java.lang.NoClassDefFoundError: org/apache/directory/api/ldap/model/filter/ExprNode at org.apache.directory.server.core.DefaultDirectoryService.<init>(DefaultDirectoryService.java:171) at org.apache.directory.server.osgi.integ.ServerCoreOsgiTest.useBundleClasses(ServerCoreOsgiTest.java:44) at org.apache.directory.server.osgi.integ.ServerOsgiTestBase.testUseBundleClasses(ServerOsgiTestBase.java:151)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runLeafWithRetry(ContainerTestRunner.java:97) at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChildWithRetry(ContainerTestRunner.java:84) at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:75) at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:43)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.invokeViaJUnit(JUnitProbeInvoker.java:124) at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.findAndInvoke(JUnitProbeInvoker.java:97) at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.call(JUnitProbeInvoker.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.ops4j.pax.swissbox.framework.RemoteFrameworkImpl.invokeMethodOnService(RemoteFrameworkImpl.java:435) at org.ops4j.pax.swissbox.framework.RemoteFrameworkImpl.invokeMethodOnService(RemoteFrameworkImpl.java:408)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: org.apache.directory.api.ldap.model.filter.ExprNode not found by org.apache.directory.server.core [62] at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1597) at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1982)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
... 49 more

On Thu, Mar 26, 2020 at 8:57 AM Emmanuel Lécharny <[email protected] <mailto:[email protected]>> wrote:

    Hi Colm,


    I will need the OSGi errors, otherwise I won't be able to know what's
    missing.


    FTR, I have it building on my Mac.

    On 26/03/2020 08:48, Colm O hEigeartaigh wrote:
    > I still have two failing tests in osgi-integ:
    >
    > [ERROR] Errors:
    > [ERROR]
    >
    
org.apache.directory.server.osgi.integ.ServerCoreAnnotationsOsgiTest.testUseBundleClasses(org.apache.directory.server.osgi.integ.ServerCoreAnnotationsOsgiTest)
    > [ERROR]   Run 1:
    >
    
ServerCoreAnnotationsOsgiTest>ServerOsgiTestBase.testUseBundleClasses:151->useBundleClasses:43

    > » ClassNotFound
    > [ERROR]   Run 2:
    >
    
ServerCoreAnnotationsOsgiTest>ServerOsgiTestBase.testUseBundleClasses:151->useBundleClasses:43

    > » ClassNotFound
    > [INFO]
    > [ERROR]
    >
    
org.apache.directory.server.osgi.integ.ServerCoreOsgiTest.testUseBundleClasses(org.apache.directory.server.osgi.integ.ServerCoreOsgiTest)
    > [ERROR]   Run 1:
    >
    
ServerCoreOsgiTest>ServerOsgiTestBase.testUseBundleClasses:151->useBundleClasses:43

    > » ClassNotFound
    > [ERROR]   Run 2:
    >
    
ServerCoreOsgiTest>ServerOsgiTestBase.testUseBundleClasses:151->useBundleClasses:43

    > » ClassNotFound
    > [INFO]
    >
    > On Wed, Mar 25, 2020 at 11:52 PM Emmanuel Lécharny
    > <[email protected] <mailto:[email protected]>
    <mailto:[email protected] <mailto:[email protected]>>> wrote:
    >
    >     I just pushed a fix. It builds now on my computer.
    >
    >     I bumped up the commons.codec and commons.pool2 dependencies on
    >     ApacheDS, they were using older versions compared to LDAP API.
    >
    >
    >
    >     On 25/03/2020 10:38, Colm O hEigeartaigh wrote:
    >     > The OSGi tests are also failing:
    >     >
    >     > ERROR: Bundle
    org.apache.directory.server.http.directory.bridge
    >     [95]
    >     > Error starting
    >     >
    >
     
file:/home/coheig/src/apache/directory-server/osgi-integ/target/1585128496666-0/pax-exam-downloads/org.apache.directory.server.http.directory.bridge_2.0.0.AM27-SNAPSHOT.jar
    >
    >     > (org.osgi.framework.BundleException: Unable to resolve
    >     > org.apache.directory.server.http.directory.bridge [95](R
    95.0):
    >     > missing requirement
    >     [org.apache.directory.server.http.directory.bridge
    >     > [95](R 95.0)] osgi.wiring.package;
    >     >
    >
     
(&(osgi.wiring.package=org.apache.directory.api.ldap.model.schema)(version>=2.0.1))
    >
    >     > [caused by: Unable to resolve
    org.apache.directory.api.ldap.model
    >     > [89](R 89.0): missing requirement
    >     [org.apache.directory.api.ldap.model
    >     > [89](R 89.0)] osgi.wiring.package;
    >     >
    >
     (&(osgi.wiring.package=org.apache.commons.codec.digest)(version>=1.14.0))]
    >
    >     > Unresolved requirements:
    >     > [[org.apache.directory.server.http.directory.bridge [95](R
    95.0)]
    >     > osgi.wiring.package;
    >     >
    >
     
(&(osgi.wiring.package=org.apache.directory.api.ldap.model.schema)(version>=2.0.1))])
    >     >
    >     > Colm.
    >     >
    >     > On Tue, Mar 24, 2020 at 11:14 PM Emmanuel Lécharny
    >     > <[email protected] <mailto:[email protected]>
    <mailto:[email protected] <mailto:[email protected]>>
    >     <mailto:[email protected] <mailto:[email protected]>
    <mailto:[email protected] <mailto:[email protected]>>>> wrote:
    >     >
    >     >
    >     >     On 24/03/2020 10:57, Colm O hEigeartaigh wrote:
    >     >     > OK thanks Emmanuel. Should we merge a fix just to
    @Ignore the
    >     >     tests then?
    >     >
    >     >     Yes, I think so.
    >     >
    >     >     If you could create a JIRA about the fact this control is
    >     seen as
    >     >     support in the RootDSE when it's not, that would help.
    >     >
    >     >
    >     >     Thanks Colm !
    >     >
    >     >
    >     >
    >     >
    >
      ---------------------------------------------------------------------
    >     >     To unsubscribe, e-mail:
    [email protected]
    <mailto:[email protected]>
    >     <mailto:[email protected]
    <mailto:[email protected]>>
    >     >     <mailto:[email protected]
    <mailto:[email protected]>
    >     <mailto:[email protected]
    <mailto:[email protected]>>>
    >     >     For additional commands, e-mail:
    > [email protected]
    <mailto:[email protected]>
    <mailto:[email protected]
    <mailto:[email protected]>>
    >     >     <mailto:[email protected]
    <mailto:[email protected]>
    >     <mailto:[email protected]
    <mailto:[email protected]>>>
    >     >
    >
    >
     ---------------------------------------------------------------------
    >     To unsubscribe, e-mail: [email protected]
    <mailto:[email protected]>
    >     <mailto:[email protected]
    <mailto:[email protected]>>
    >     For additional commands, e-mail:
    [email protected] <mailto:[email protected]>
    >     <mailto:[email protected]
    <mailto:[email protected]>>
    >


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to