Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
Resolved in r1900112. I created both the overlay configurations for Ant and Maven. Il giorno gio 21 apr 2022 alle ore 13:04 Karl Wright ha scritto: > Sounds like a good idea. > One suggestion: I would not structure the ant logic to overwrite the war. > I would download one copy and then transfer/create a different copy. Ant > works best that way. So no deletion of the original download. > > On Thu, Apr 21, 2022 at 6:59 AM Piergiorgio Lucidi > > wrote: > > > I'm going to patch the the WAR file in the download-dependencies task in > > Ant :-P > > I'll use the download-via-maven for downloading all the libraries to > > update, then unzip, delete and the jar task, so it should be enough, what > > do you think? > > PJ > > > > Il giorno gio 21 apr 2022 alle ore 12:49 Karl Wright > > > ha scritto: > > > > > Right now the war is downloaded via ant, I think. We should "patch" it > > > when we download it, by unpacking, updating, and repacking. We leave > it > > in > > > a specific place and I don't believe the pom.xml refers to it directly. > > > > > > If you can confirm that picture, I can suggest ant commands to do the > > > unpack / copy / repack. Or I can look at this much later today myself. > > > > > > Karl > > > > > > > > > On Thu, Apr 21, 2022 at 6:46 AM Piergiorgio Lucidi < > > piergior...@apache.org > > > > > > > wrote: > > > > > > > Ok I solved the classloading issue :) > > > > > > > > I found all the dependencies that we have to update in the OpenCMIS > > > Server > > > > WAR, practically we have to: > > > > 1. Update log4j from 2.6.1 to 2.17.2 > > > > 2. Update CXF from 3.0.12 to 3.5.2 > > > > 3. Add activation-1.1.1.jar > > > > 4. Add jaxws-api-2.3.1.jar > > > > > > > > Here the list of dependencies that we have to remove from the WAR: > > > > > > > >- cxf-core-3.0.12.jar > > > >- cxf-rt-bindings-soap-3.0.12.jar > > > >- cxf-rt-bindings-xml-3.0.12.jar > > > >- cxf-rt-databinding-jaxb-3.0.12.jar > > > >- cxf-rt-frontend-jaxws-3.0.12.jar > > > >- cxf-rt-frontend-simple-3.0.12.jar > > > >- cxf-rt-transports-http-3.0.12.jar > > > >- cxf-rt-ws-addr-3.0.12.jar > > > >- cxf-rt-ws-policy-3.0.12.jar > > > >- cxf-rt-wsdl-3.0.12.jar > > > >- log4j-slf4j-impl-2.6.1.jar > > > >- log4j-core-2.6.1.jar > > > >- log4j-api-2.6.1.jar > > > > > > > > And below the list of JARs to add in the WAR: > > > > > > > >- jax-ws-api-2.3.1.jar > > > >- log4j-slf4j-impl-2.17.2.jar > > > >- log4j-core-2.17.2.jar > > > >- log4j-api-2.17.2.jar > > > >- activation-1.1.1.jar > > > >- cxf-core-3.0.12.jar > > > >- cxf-rt-bindings-soap-3.5.2.jar > > > >- cxf-rt-bindings-xml-3.5.2.jar > > > >- cxf-rt-databinding-jaxb-3.5.2.jar > > > >- cxf-rt-frontend-jaxws-3.5.2.jar > > > >- cxf-rt-frontend-simple-3.5.2.jar > > > >- cxf-rt-transports-http-3.5.2.jar > > > >- cxf-rt-ws-addr-3.5.2.jar > > > >- cxf-rt-ws-policy-3.5.2.jar > > > >- cxf-rt-wsdl-3.5.2.jar > > > > > > > > We only need to overlay the > > chemistry-opencmis-server-inmemory-1.1.0.war > > > > updating log4j and cxf dependencies in order to solve the deployment > > > issue. > > > > I ran tests correctly using the new WAR file. > > > > > > > > What could be the best way to overlay the WAR for making it available > > for > > > > both Ant and Maven? > > > > Maybe using an Ant script and then reuse the same in Maven? > > > > > > > > Cheers, > > > > PJ > > > > > > > > Il giorno gio 21 apr 2022 alle ore 12:27 Karl Wright < > > daddy...@gmail.com > > > > > > > > ha scritto: > > > > > > > > > Ok, maybe there's a conflict then. We cannot back out versions of > > CXF > > > > > because we use that for the Livelink connector now. > > > > > > > > > > > > > > > On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi < > > > > piergior...@apache.org > > > > > > > > > > > wrote: > > > > > > > > > > > Sure, I'm investigating the OpenCMIS Server issue, I resolved the > > > Log4j > > > > > > issue updating the jar in the WAR but now I see a problem with > CXF > > > old > > > > > > dependencies. > > > > > > The strange thing is that using the same patched WAR in a > standard > > > > Docker > > > > > > container based on OpenJDK 11 it works perfectly but trying to > use > > it > > > > > using > > > > > > Ant or Maven return issues. > > > > > > > > > > > > We could disable integration tests for CMIS connectors eventually > > for > > > > > this > > > > > > release. > > > > > > > > > > > > Probably it will take some time to understand all the > dependencies > > to > > > > > > update in the OpenCMIS Server, anyway when I have a working WAR > > file > > > > then > > > > > > we should create an ant script to update everything starting from > > the > > > > > > original distribution WAR. > > > > > > > > > > > > I'll keep you updated. > > > > > > > > > > > > Cheers, > > > > > > PJ > > > > > > > > > > > > Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright < > > > > daddy...@gmail.com > > > > > > > >
Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
Sounds like a good idea. One suggestion: I would not structure the ant logic to overwrite the war. I would download one copy and then transfer/create a different copy. Ant works best that way. So no deletion of the original download. On Thu, Apr 21, 2022 at 6:59 AM Piergiorgio Lucidi wrote: > I'm going to patch the the WAR file in the download-dependencies task in > Ant :-P > I'll use the download-via-maven for downloading all the libraries to > update, then unzip, delete and the jar task, so it should be enough, what > do you think? > PJ > > Il giorno gio 21 apr 2022 alle ore 12:49 Karl Wright > ha scritto: > > > Right now the war is downloaded via ant, I think. We should "patch" it > > when we download it, by unpacking, updating, and repacking. We leave it > in > > a specific place and I don't believe the pom.xml refers to it directly. > > > > If you can confirm that picture, I can suggest ant commands to do the > > unpack / copy / repack. Or I can look at this much later today myself. > > > > Karl > > > > > > On Thu, Apr 21, 2022 at 6:46 AM Piergiorgio Lucidi < > piergior...@apache.org > > > > > wrote: > > > > > Ok I solved the classloading issue :) > > > > > > I found all the dependencies that we have to update in the OpenCMIS > > Server > > > WAR, practically we have to: > > > 1. Update log4j from 2.6.1 to 2.17.2 > > > 2. Update CXF from 3.0.12 to 3.5.2 > > > 3. Add activation-1.1.1.jar > > > 4. Add jaxws-api-2.3.1.jar > > > > > > Here the list of dependencies that we have to remove from the WAR: > > > > > >- cxf-core-3.0.12.jar > > >- cxf-rt-bindings-soap-3.0.12.jar > > >- cxf-rt-bindings-xml-3.0.12.jar > > >- cxf-rt-databinding-jaxb-3.0.12.jar > > >- cxf-rt-frontend-jaxws-3.0.12.jar > > >- cxf-rt-frontend-simple-3.0.12.jar > > >- cxf-rt-transports-http-3.0.12.jar > > >- cxf-rt-ws-addr-3.0.12.jar > > >- cxf-rt-ws-policy-3.0.12.jar > > >- cxf-rt-wsdl-3.0.12.jar > > >- log4j-slf4j-impl-2.6.1.jar > > >- log4j-core-2.6.1.jar > > >- log4j-api-2.6.1.jar > > > > > > And below the list of JARs to add in the WAR: > > > > > >- jax-ws-api-2.3.1.jar > > >- log4j-slf4j-impl-2.17.2.jar > > >- log4j-core-2.17.2.jar > > >- log4j-api-2.17.2.jar > > >- activation-1.1.1.jar > > >- cxf-core-3.0.12.jar > > >- cxf-rt-bindings-soap-3.5.2.jar > > >- cxf-rt-bindings-xml-3.5.2.jar > > >- cxf-rt-databinding-jaxb-3.5.2.jar > > >- cxf-rt-frontend-jaxws-3.5.2.jar > > >- cxf-rt-frontend-simple-3.5.2.jar > > >- cxf-rt-transports-http-3.5.2.jar > > >- cxf-rt-ws-addr-3.5.2.jar > > >- cxf-rt-ws-policy-3.5.2.jar > > >- cxf-rt-wsdl-3.5.2.jar > > > > > > We only need to overlay the > chemistry-opencmis-server-inmemory-1.1.0.war > > > updating log4j and cxf dependencies in order to solve the deployment > > issue. > > > I ran tests correctly using the new WAR file. > > > > > > What could be the best way to overlay the WAR for making it available > for > > > both Ant and Maven? > > > Maybe using an Ant script and then reuse the same in Maven? > > > > > > Cheers, > > > PJ > > > > > > Il giorno gio 21 apr 2022 alle ore 12:27 Karl Wright < > daddy...@gmail.com > > > > > > ha scritto: > > > > > > > Ok, maybe there's a conflict then. We cannot back out versions of > CXF > > > > because we use that for the Livelink connector now. > > > > > > > > > > > > On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi < > > > piergior...@apache.org > > > > > > > > > wrote: > > > > > > > > > Sure, I'm investigating the OpenCMIS Server issue, I resolved the > > Log4j > > > > > issue updating the jar in the WAR but now I see a problem with CXF > > old > > > > > dependencies. > > > > > The strange thing is that using the same patched WAR in a standard > > > Docker > > > > > container based on OpenJDK 11 it works perfectly but trying to use > it > > > > using > > > > > Ant or Maven return issues. > > > > > > > > > > We could disable integration tests for CMIS connectors eventually > for > > > > this > > > > > release. > > > > > > > > > > Probably it will take some time to understand all the dependencies > to > > > > > update in the OpenCMIS Server, anyway when I have a working WAR > file > > > then > > > > > we should create an ant script to update everything starting from > the > > > > > original distribution WAR. > > > > > > > > > > I'll keep you updated. > > > > > > > > > > Cheers, > > > > > PJ > > > > > > > > > > Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright < > > > daddy...@gmail.com > > > > > > > > > > ha scritto: > > > > > > > > > > > I can fix the bad pom but not the CMIS issue, which will require > > more > > > > > > research. > > > > > > Karl > > > > > > > > > > > > On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi < > > > > > piergior...@apache.org > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi Karl, > > > > > > > > > > > > > > -1 from me because I found these problems: > > > > > > > > > > > > > > 1. Trying to
Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
I'm going to patch the the WAR file in the download-dependencies task in Ant :-P I'll use the download-via-maven for downloading all the libraries to update, then unzip, delete and the jar task, so it should be enough, what do you think? PJ Il giorno gio 21 apr 2022 alle ore 12:49 Karl Wright ha scritto: > Right now the war is downloaded via ant, I think. We should "patch" it > when we download it, by unpacking, updating, and repacking. We leave it in > a specific place and I don't believe the pom.xml refers to it directly. > > If you can confirm that picture, I can suggest ant commands to do the > unpack / copy / repack. Or I can look at this much later today myself. > > Karl > > > On Thu, Apr 21, 2022 at 6:46 AM Piergiorgio Lucidi > > wrote: > > > Ok I solved the classloading issue :) > > > > I found all the dependencies that we have to update in the OpenCMIS > Server > > WAR, practically we have to: > > 1. Update log4j from 2.6.1 to 2.17.2 > > 2. Update CXF from 3.0.12 to 3.5.2 > > 3. Add activation-1.1.1.jar > > 4. Add jaxws-api-2.3.1.jar > > > > Here the list of dependencies that we have to remove from the WAR: > > > >- cxf-core-3.0.12.jar > >- cxf-rt-bindings-soap-3.0.12.jar > >- cxf-rt-bindings-xml-3.0.12.jar > >- cxf-rt-databinding-jaxb-3.0.12.jar > >- cxf-rt-frontend-jaxws-3.0.12.jar > >- cxf-rt-frontend-simple-3.0.12.jar > >- cxf-rt-transports-http-3.0.12.jar > >- cxf-rt-ws-addr-3.0.12.jar > >- cxf-rt-ws-policy-3.0.12.jar > >- cxf-rt-wsdl-3.0.12.jar > >- log4j-slf4j-impl-2.6.1.jar > >- log4j-core-2.6.1.jar > >- log4j-api-2.6.1.jar > > > > And below the list of JARs to add in the WAR: > > > >- jax-ws-api-2.3.1.jar > >- log4j-slf4j-impl-2.17.2.jar > >- log4j-core-2.17.2.jar > >- log4j-api-2.17.2.jar > >- activation-1.1.1.jar > >- cxf-core-3.0.12.jar > >- cxf-rt-bindings-soap-3.5.2.jar > >- cxf-rt-bindings-xml-3.5.2.jar > >- cxf-rt-databinding-jaxb-3.5.2.jar > >- cxf-rt-frontend-jaxws-3.5.2.jar > >- cxf-rt-frontend-simple-3.5.2.jar > >- cxf-rt-transports-http-3.5.2.jar > >- cxf-rt-ws-addr-3.5.2.jar > >- cxf-rt-ws-policy-3.5.2.jar > >- cxf-rt-wsdl-3.5.2.jar > > > > We only need to overlay the chemistry-opencmis-server-inmemory-1.1.0.war > > updating log4j and cxf dependencies in order to solve the deployment > issue. > > I ran tests correctly using the new WAR file. > > > > What could be the best way to overlay the WAR for making it available for > > both Ant and Maven? > > Maybe using an Ant script and then reuse the same in Maven? > > > > Cheers, > > PJ > > > > Il giorno gio 21 apr 2022 alle ore 12:27 Karl Wright > > > ha scritto: > > > > > Ok, maybe there's a conflict then. We cannot back out versions of CXF > > > because we use that for the Livelink connector now. > > > > > > > > > On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi < > > piergior...@apache.org > > > > > > > wrote: > > > > > > > Sure, I'm investigating the OpenCMIS Server issue, I resolved the > Log4j > > > > issue updating the jar in the WAR but now I see a problem with CXF > old > > > > dependencies. > > > > The strange thing is that using the same patched WAR in a standard > > Docker > > > > container based on OpenJDK 11 it works perfectly but trying to use it > > > using > > > > Ant or Maven return issues. > > > > > > > > We could disable integration tests for CMIS connectors eventually for > > > this > > > > release. > > > > > > > > Probably it will take some time to understand all the dependencies to > > > > update in the OpenCMIS Server, anyway when I have a working WAR file > > then > > > > we should create an ant script to update everything starting from the > > > > original distribution WAR. > > > > > > > > I'll keep you updated. > > > > > > > > Cheers, > > > > PJ > > > > > > > > Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright < > > daddy...@gmail.com > > > > > > > > ha scritto: > > > > > > > > > I can fix the bad pom but not the CMIS issue, which will require > more > > > > > research. > > > > > Karl > > > > > > > > > > On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi < > > > > piergior...@apache.org > > > > > > > > > > > wrote: > > > > > > > > > > > Hi Karl, > > > > > > > > > > > > -1 from me because I found these problems: > > > > > > > > > > > > 1. Trying to build with Maven I see the following error: > > > > > > > > > > > > The build could not read 1 project -> [Help 1] > > > > > > [ERROR] > > > > > > [ERROR] The project > > > > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT > > > > > > > > > > > > > > > > > > > > > > > > > > > (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) > > > > > > has 1 error > > > > > > [ERROR] Non-resolvable parent POM for > > > > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: > Could > > > not > > > > > > find artifact > > org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT > > > > and
Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
Right now the war is downloaded via ant, I think. We should "patch" it when we download it, by unpacking, updating, and repacking. We leave it in a specific place and I don't believe the pom.xml refers to it directly. If you can confirm that picture, I can suggest ant commands to do the unpack / copy / repack. Or I can look at this much later today myself. Karl On Thu, Apr 21, 2022 at 6:46 AM Piergiorgio Lucidi wrote: > Ok I solved the classloading issue :) > > I found all the dependencies that we have to update in the OpenCMIS Server > WAR, practically we have to: > 1. Update log4j from 2.6.1 to 2.17.2 > 2. Update CXF from 3.0.12 to 3.5.2 > 3. Add activation-1.1.1.jar > 4. Add jaxws-api-2.3.1.jar > > Here the list of dependencies that we have to remove from the WAR: > >- cxf-core-3.0.12.jar >- cxf-rt-bindings-soap-3.0.12.jar >- cxf-rt-bindings-xml-3.0.12.jar >- cxf-rt-databinding-jaxb-3.0.12.jar >- cxf-rt-frontend-jaxws-3.0.12.jar >- cxf-rt-frontend-simple-3.0.12.jar >- cxf-rt-transports-http-3.0.12.jar >- cxf-rt-ws-addr-3.0.12.jar >- cxf-rt-ws-policy-3.0.12.jar >- cxf-rt-wsdl-3.0.12.jar >- log4j-slf4j-impl-2.6.1.jar >- log4j-core-2.6.1.jar >- log4j-api-2.6.1.jar > > And below the list of JARs to add in the WAR: > >- jax-ws-api-2.3.1.jar >- log4j-slf4j-impl-2.17.2.jar >- log4j-core-2.17.2.jar >- log4j-api-2.17.2.jar >- activation-1.1.1.jar >- cxf-core-3.0.12.jar >- cxf-rt-bindings-soap-3.5.2.jar >- cxf-rt-bindings-xml-3.5.2.jar >- cxf-rt-databinding-jaxb-3.5.2.jar >- cxf-rt-frontend-jaxws-3.5.2.jar >- cxf-rt-frontend-simple-3.5.2.jar >- cxf-rt-transports-http-3.5.2.jar >- cxf-rt-ws-addr-3.5.2.jar >- cxf-rt-ws-policy-3.5.2.jar >- cxf-rt-wsdl-3.5.2.jar > > We only need to overlay the chemistry-opencmis-server-inmemory-1.1.0.war > updating log4j and cxf dependencies in order to solve the deployment issue. > I ran tests correctly using the new WAR file. > > What could be the best way to overlay the WAR for making it available for > both Ant and Maven? > Maybe using an Ant script and then reuse the same in Maven? > > Cheers, > PJ > > Il giorno gio 21 apr 2022 alle ore 12:27 Karl Wright > ha scritto: > > > Ok, maybe there's a conflict then. We cannot back out versions of CXF > > because we use that for the Livelink connector now. > > > > > > On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi < > piergior...@apache.org > > > > > wrote: > > > > > Sure, I'm investigating the OpenCMIS Server issue, I resolved the Log4j > > > issue updating the jar in the WAR but now I see a problem with CXF old > > > dependencies. > > > The strange thing is that using the same patched WAR in a standard > Docker > > > container based on OpenJDK 11 it works perfectly but trying to use it > > using > > > Ant or Maven return issues. > > > > > > We could disable integration tests for CMIS connectors eventually for > > this > > > release. > > > > > > Probably it will take some time to understand all the dependencies to > > > update in the OpenCMIS Server, anyway when I have a working WAR file > then > > > we should create an ant script to update everything starting from the > > > original distribution WAR. > > > > > > I'll keep you updated. > > > > > > Cheers, > > > PJ > > > > > > Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright < > daddy...@gmail.com > > > > > > ha scritto: > > > > > > > I can fix the bad pom but not the CMIS issue, which will require more > > > > research. > > > > Karl > > > > > > > > On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi < > > > piergior...@apache.org > > > > > > > > > wrote: > > > > > > > > > Hi Karl, > > > > > > > > > > -1 from me because I found these problems: > > > > > > > > > > 1. Trying to build with Maven I see the following error: > > > > > > > > > > The build could not read 1 project -> [Help 1] > > > > > [ERROR] > > > > > [ERROR] The project > > > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT > > > > > > > > > > > > > > > > > > > > (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) > > > > > has 1 error > > > > > [ERROR] Non-resolvable parent POM for > > > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: Could > > not > > > > > find artifact > org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT > > > and > > > > > 'parent.relativePath' points at wrong local POM @ line 2, column 11 > > -> > > > > > [Help 2] > > > > > > > > > > So it seems that the version is wrong in the new LDAP Mapper > > Connector, > > > > so > > > > > updating the version element from 2.22-SNAPSHOT to 2.22 in that pom > > > then > > > > > the build starts correctly. > > > > > > > > > > 2. Trying to execute tests with Ant or Maven, I see a problem > > related > > > to > > > > > the OpenCMIS server during the execution of integration tests > related > > > to > > > > > the CMIS Connectors. It's a classCastException related to
Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
Ok I solved the classloading issue :) I found all the dependencies that we have to update in the OpenCMIS Server WAR, practically we have to: 1. Update log4j from 2.6.1 to 2.17.2 2. Update CXF from 3.0.12 to 3.5.2 3. Add activation-1.1.1.jar 4. Add jaxws-api-2.3.1.jar Here the list of dependencies that we have to remove from the WAR: - cxf-core-3.0.12.jar - cxf-rt-bindings-soap-3.0.12.jar - cxf-rt-bindings-xml-3.0.12.jar - cxf-rt-databinding-jaxb-3.0.12.jar - cxf-rt-frontend-jaxws-3.0.12.jar - cxf-rt-frontend-simple-3.0.12.jar - cxf-rt-transports-http-3.0.12.jar - cxf-rt-ws-addr-3.0.12.jar - cxf-rt-ws-policy-3.0.12.jar - cxf-rt-wsdl-3.0.12.jar - log4j-slf4j-impl-2.6.1.jar - log4j-core-2.6.1.jar - log4j-api-2.6.1.jar And below the list of JARs to add in the WAR: - jax-ws-api-2.3.1.jar - log4j-slf4j-impl-2.17.2.jar - log4j-core-2.17.2.jar - log4j-api-2.17.2.jar - activation-1.1.1.jar - cxf-core-3.0.12.jar - cxf-rt-bindings-soap-3.5.2.jar - cxf-rt-bindings-xml-3.5.2.jar - cxf-rt-databinding-jaxb-3.5.2.jar - cxf-rt-frontend-jaxws-3.5.2.jar - cxf-rt-frontend-simple-3.5.2.jar - cxf-rt-transports-http-3.5.2.jar - cxf-rt-ws-addr-3.5.2.jar - cxf-rt-ws-policy-3.5.2.jar - cxf-rt-wsdl-3.5.2.jar We only need to overlay the chemistry-opencmis-server-inmemory-1.1.0.war updating log4j and cxf dependencies in order to solve the deployment issue. I ran tests correctly using the new WAR file. What could be the best way to overlay the WAR for making it available for both Ant and Maven? Maybe using an Ant script and then reuse the same in Maven? Cheers, PJ Il giorno gio 21 apr 2022 alle ore 12:27 Karl Wright ha scritto: > Ok, maybe there's a conflict then. We cannot back out versions of CXF > because we use that for the Livelink connector now. > > > On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi > > wrote: > > > Sure, I'm investigating the OpenCMIS Server issue, I resolved the Log4j > > issue updating the jar in the WAR but now I see a problem with CXF old > > dependencies. > > The strange thing is that using the same patched WAR in a standard Docker > > container based on OpenJDK 11 it works perfectly but trying to use it > using > > Ant or Maven return issues. > > > > We could disable integration tests for CMIS connectors eventually for > this > > release. > > > > Probably it will take some time to understand all the dependencies to > > update in the OpenCMIS Server, anyway when I have a working WAR file then > > we should create an ant script to update everything starting from the > > original distribution WAR. > > > > I'll keep you updated. > > > > Cheers, > > PJ > > > > Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright > > > ha scritto: > > > > > I can fix the bad pom but not the CMIS issue, which will require more > > > research. > > > Karl > > > > > > On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi < > > piergior...@apache.org > > > > > > > wrote: > > > > > > > Hi Karl, > > > > > > > > -1 from me because I found these problems: > > > > > > > > 1. Trying to build with Maven I see the following error: > > > > > > > > The build could not read 1 project -> [Help 1] > > > > [ERROR] > > > > [ERROR] The project > > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT > > > > > > > > > > > > > > (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) > > > > has 1 error > > > > [ERROR] Non-resolvable parent POM for > > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: Could > not > > > > find artifact org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT > > and > > > > 'parent.relativePath' points at wrong local POM @ line 2, column 11 > -> > > > > [Help 2] > > > > > > > > So it seems that the version is wrong in the new LDAP Mapper > Connector, > > > so > > > > updating the version element from 2.22-SNAPSHOT to 2.22 in that pom > > then > > > > the build starts correctly. > > > > > > > > 2. Trying to execute tests with Ant or Maven, I see a problem > related > > to > > > > the OpenCMIS server during the execution of integration tests related > > to > > > > the CMIS Connectors. It's a classCastException related to Log4j, > below > > > the > > > > exception that I see: > > > > > > > > [main] INFO org.eclipse.jetty.server.Server - Started @1830ms > > > > [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.25.v20191220; > > > > built: 2019-12-20T17:00:00.294Z; git: > > > > a9729c7e7f33a459d2616a8f9e9ba8a90f432e95; jvm 11.0.13+8-LTS > > > > [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO > > JSP > > > > Support for /chemistry-opencmis-server-inmemory, did not find > > > > org.eclipse.jetty.jsp.JettyJspServlet > > > > SLF4J: Class path contains multiple SLF4J bindings. > > > > SLF4J: Found binding in > > > > > > > > > > > > > >
Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
Ok, maybe there's a conflict then. We cannot back out versions of CXF because we use that for the Livelink connector now. On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi wrote: > Sure, I'm investigating the OpenCMIS Server issue, I resolved the Log4j > issue updating the jar in the WAR but now I see a problem with CXF old > dependencies. > The strange thing is that using the same patched WAR in a standard Docker > container based on OpenJDK 11 it works perfectly but trying to use it using > Ant or Maven return issues. > > We could disable integration tests for CMIS connectors eventually for this > release. > > Probably it will take some time to understand all the dependencies to > update in the OpenCMIS Server, anyway when I have a working WAR file then > we should create an ant script to update everything starting from the > original distribution WAR. > > I'll keep you updated. > > Cheers, > PJ > > Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright > ha scritto: > > > I can fix the bad pom but not the CMIS issue, which will require more > > research. > > Karl > > > > On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi < > piergior...@apache.org > > > > > wrote: > > > > > Hi Karl, > > > > > > -1 from me because I found these problems: > > > > > > 1. Trying to build with Maven I see the following error: > > > > > > The build could not read 1 project -> [Help 1] > > > [ERROR] > > > [ERROR] The project > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT > > > > > > > > > (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) > > > has 1 error > > > [ERROR] Non-resolvable parent POM for > > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: Could not > > > find artifact org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT > and > > > 'parent.relativePath' points at wrong local POM @ line 2, column 11 -> > > > [Help 2] > > > > > > So it seems that the version is wrong in the new LDAP Mapper Connector, > > so > > > updating the version element from 2.22-SNAPSHOT to 2.22 in that pom > then > > > the build starts correctly. > > > > > > 2. Trying to execute tests with Ant or Maven, I see a problem related > to > > > the OpenCMIS server during the execution of integration tests related > to > > > the CMIS Connectors. It's a classCastException related to Log4j, below > > the > > > exception that I see: > > > > > > [main] INFO org.eclipse.jetty.server.Server - Started @1830ms > > > [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.25.v20191220; > > > built: 2019-12-20T17:00:00.294Z; git: > > > a9729c7e7f33a459d2616a8f9e9ba8a90f432e95; jvm 11.0.13+8-LTS > > > [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO > JSP > > > Support for /chemistry-opencmis-server-inmemory, did not find > > > org.eclipse.jetty.jsp.JettyJspServlet > > > SLF4J: Class path contains multiple SLF4J bindings. > > > SLF4J: Found binding in > > > > > > > > > [jar:file:/private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-9090-chemistry-opencmis-server-inmemory_war-_chemistry-opencmis-server-inmemory-any-6022774582585212771.dir/webapp/WEB-INF/lib/log4j-slf4j-impl-2.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > > > SLF4J: Found binding in > > > > > > > > > [jar:file:/Users/pjlucidi/.m2/repository/org/slf4j/slf4j-simple/1.7.7/slf4j-simple-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] > > > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > > > explanation. > > > SLF4J: Actual binding is of type > > > [org.apache.logging.slf4j.Log4jLoggerFactory] > > > 2022-04-21 11:49:07,026 main ERROR Unable to create Lookup for event > > > java.lang.ClassCastException: class > > > org.apache.logging.log4j.core.lookup.EventLookup > > > at java.base/java.lang.Class.asSubclass(Class.java:3640) > > > at > > > > > > > > > org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:65) > > > at > > > > > > > > > org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:467) > > > at > > > > > > > > > org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219) > > > at > > > > > > > > > org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231) > > > at > > > > > > > > > org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491) > > > at > > > > > > > > > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561) > > > at > > > > > > > > > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577) > > > at > > > > org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212) > > > at > > > > > > > > > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) > > > at > > > > > > > > > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) > > > at
Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
Sure, I'm investigating the OpenCMIS Server issue, I resolved the Log4j issue updating the jar in the WAR but now I see a problem with CXF old dependencies. The strange thing is that using the same patched WAR in a standard Docker container based on OpenJDK 11 it works perfectly but trying to use it using Ant or Maven return issues. We could disable integration tests for CMIS connectors eventually for this release. Probably it will take some time to understand all the dependencies to update in the OpenCMIS Server, anyway when I have a working WAR file then we should create an ant script to update everything starting from the original distribution WAR. I'll keep you updated. Cheers, PJ Il giorno gio 21 apr 2022 alle ore 12:11 Karl Wright ha scritto: > I can fix the bad pom but not the CMIS issue, which will require more > research. > Karl > > On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi > > wrote: > > > Hi Karl, > > > > -1 from me because I found these problems: > > > > 1. Trying to build with Maven I see the following error: > > > > The build could not read 1 project -> [Help 1] > > [ERROR] > > [ERROR] The project > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT > > > > > (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) > > has 1 error > > [ERROR] Non-resolvable parent POM for > > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: Could not > > find artifact org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT and > > 'parent.relativePath' points at wrong local POM @ line 2, column 11 -> > > [Help 2] > > > > So it seems that the version is wrong in the new LDAP Mapper Connector, > so > > updating the version element from 2.22-SNAPSHOT to 2.22 in that pom then > > the build starts correctly. > > > > 2. Trying to execute tests with Ant or Maven, I see a problem related to > > the OpenCMIS server during the execution of integration tests related to > > the CMIS Connectors. It's a classCastException related to Log4j, below > the > > exception that I see: > > > > [main] INFO org.eclipse.jetty.server.Server - Started @1830ms > > [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.25.v20191220; > > built: 2019-12-20T17:00:00.294Z; git: > > a9729c7e7f33a459d2616a8f9e9ba8a90f432e95; jvm 11.0.13+8-LTS > > [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO JSP > > Support for /chemistry-opencmis-server-inmemory, did not find > > org.eclipse.jetty.jsp.JettyJspServlet > > SLF4J: Class path contains multiple SLF4J bindings. > > SLF4J: Found binding in > > > > > [jar:file:/private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-9090-chemistry-opencmis-server-inmemory_war-_chemistry-opencmis-server-inmemory-any-6022774582585212771.dir/webapp/WEB-INF/lib/log4j-slf4j-impl-2.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > > SLF4J: Found binding in > > > > > [jar:file:/Users/pjlucidi/.m2/repository/org/slf4j/slf4j-simple/1.7.7/slf4j-simple-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] > > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > > explanation. > > SLF4J: Actual binding is of type > > [org.apache.logging.slf4j.Log4jLoggerFactory] > > 2022-04-21 11:49:07,026 main ERROR Unable to create Lookup for event > > java.lang.ClassCastException: class > > org.apache.logging.log4j.core.lookup.EventLookup > > at java.base/java.lang.Class.asSubclass(Class.java:3640) > > at > > > > > org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:65) > > at > > > > > org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:467) > > at > > > > > org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219) > > at > > > > > org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231) > > at > > > > > org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491) > > at > > > > > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561) > > at > > > > > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577) > > at > > org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212) > > at > > > > > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) > > at > > > > > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) > > at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) > > at > > > > > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103) > > at > > > > > org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43) > > at > > > > > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42) > > at > > > > > org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29) > >
[CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC0
I can fix the bad pom but not the CMIS issue, which will require more research. Karl On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi wrote: > Hi Karl, > > -1 from me because I found these problems: > > 1. Trying to build with Maven I see the following error: > > The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT > > (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: Could not > find artifact org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 2, column 11 -> > [Help 2] > > So it seems that the version is wrong in the new LDAP Mapper Connector, so > updating the version element from 2.22-SNAPSHOT to 2.22 in that pom then > the build starts correctly. > > 2. Trying to execute tests with Ant or Maven, I see a problem related to > the OpenCMIS server during the execution of integration tests related to > the CMIS Connectors. It's a classCastException related to Log4j, below the > exception that I see: > > [main] INFO org.eclipse.jetty.server.Server - Started @1830ms > [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.25.v20191220; > built: 2019-12-20T17:00:00.294Z; git: > a9729c7e7f33a459d2616a8f9e9ba8a90f432e95; jvm 11.0.13+8-LTS > [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO JSP > Support for /chemistry-opencmis-server-inmemory, did not find > org.eclipse.jetty.jsp.JettyJspServlet > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > > [jar:file:/private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-9090-chemistry-opencmis-server-inmemory_war-_chemistry-opencmis-server-inmemory-any-6022774582585212771.dir/webapp/WEB-INF/lib/log4j-slf4j-impl-2.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > > [jar:file:/Users/pjlucidi/.m2/repository/org/slf4j/slf4j-simple/1.7.7/slf4j-simple-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type > [org.apache.logging.slf4j.Log4jLoggerFactory] > 2022-04-21 11:49:07,026 main ERROR Unable to create Lookup for event > java.lang.ClassCastException: class > org.apache.logging.log4j.core.lookup.EventLookup > at java.base/java.lang.Class.asSubclass(Class.java:3640) > at > > org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:65) > at > > org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:467) > at > > org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219) > at > > org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231) > at > > org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491) > at > > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561) > at > > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577) > at > org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212) > at > > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) > at > > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) > at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) > at > > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103) > at > > org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43) > at > > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42) > at > > org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358) > at > > org.apache.chemistry.opencmis.server.impl.CmisRepositoryContextListener.(CmisRepositoryContextListener.java:45) > at > > java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > > java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > > java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) > at > > org.eclipse.jetty.server.handler.ContextHandler$StaticContext.createInstance(ContextHandler.java:2784) > at > > org.eclipse.jetty.servlet.ServletContextHandler$Context.createInstance(ServletContextHandler.java:1280) > at > > org.eclipse.jetty.server.handler.ContextHandler$StaticContext.createListener(ContextHandler.java:2795) > at
Re: [VOTE] Release Apache ManifoldCF 2.22, RC0
Hi Karl, -1 from me because I found these problems: 1. Trying to build with Maven I see the following error: The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT (/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/connectors/ldapmapper/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for org.apache.manifoldcf:mcf-ldapmapper-connector:2.22-SNAPSHOT: Could not find artifact org.apache.manifoldcf:mcf-connectors:pom:2.22-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 2, column 11 -> [Help 2] So it seems that the version is wrong in the new LDAP Mapper Connector, so updating the version element from 2.22-SNAPSHOT to 2.22 in that pom then the build starts correctly. 2. Trying to execute tests with Ant or Maven, I see a problem related to the OpenCMIS server during the execution of integration tests related to the CMIS Connectors. It's a classCastException related to Log4j, below the exception that I see: [main] INFO org.eclipse.jetty.server.Server - Started @1830ms [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.25.v20191220; built: 2019-12-20T17:00:00.294Z; git: a9729c7e7f33a459d2616a8f9e9ba8a90f432e95; jvm 11.0.13+8-LTS [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO JSP Support for /chemistry-opencmis-server-inmemory, did not find org.eclipse.jetty.jsp.JettyJspServlet SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-9090-chemistry-opencmis-server-inmemory_war-_chemistry-opencmis-server-inmemory-any-6022774582585212771.dir/webapp/WEB-INF/lib/log4j-slf4j-impl-2.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/pjlucidi/.m2/repository/org/slf4j/slf4j-simple/1.7.7/slf4j-simple-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] 2022-04-21 11:49:07,026 main ERROR Unable to create Lookup for event java.lang.ClassCastException: class org.apache.logging.log4j.core.lookup.EventLookup at java.base/java.lang.Class.asSubclass(Class.java:3640) at org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:65) at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:467) at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219) at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231) at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103) at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42) at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358) at org.apache.chemistry.opencmis.server.impl.CmisRepositoryContextListener.(CmisRepositoryContextListener.java:45) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.eclipse.jetty.server.handler.ContextHandler$StaticContext.createInstance(ContextHandler.java:2784) at org.eclipse.jetty.servlet.ServletContextHandler$Context.createInstance(ServletContextHandler.java:1280) at org.eclipse.jetty.server.handler.ContextHandler$StaticContext.createListener(ContextHandler.java:2795) at org.eclipse.jetty.servlet.ListenerHolder.doStart(ListenerHolder.java:92) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:350) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1445) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409) at
[VOTE] Release Apache ManifoldCF 2.22, RC0
Hi, Please vote on whether to release Apache ManifoldCF 2.22, RC0. The release artifact is at https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.22 . There is also a release tag at https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.22-RC0 . This release contains a Tika update which required extensive dependency updates, which needs some degree of testing, as well as a new LDAP Mapper. Thanks in advance, Karl
