Build failed in Jenkins: ManifoldCF » ManifoldCF-ant #81

2023-10-09 Thread Apache Jenkins Server
See 


Changes:

[Karl Wright] Restore native2ascii invocation

[Karl Wright] Prepare trunk for 2.27 development

[Karl Wright] Tie off release 2.26


--
[...truncated 204.45 KB...]

setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/brotli/dec/0.1.2/dec-0.1.2.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/jempbox/1.8.16/jempbox-1.8.16.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox/2.0.25/pdfbox-2.0.25.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/fontbox/2.0.25/fontbox-2.0.25.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/preflight/2.0.25/preflight-2.0.25.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/xmpbox/2.0.25/xmpbox-2.0.25.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox-debugger/2.0.25/pdfbox-debugger-2.0.25.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox-tools/2.0.25/pdfbox-tools-2.0.25.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.21/commons-compress-1.21.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/com/googlecode/juniversalchardet/juniversalchardet/1.0.3/juniversalchardet-1.0.3.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/de/l3s/boilerpipe/boilerpipe/1.1.0/boilerpipe-1.1.0.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/tallison/xmp/xmpcore-shaded/6.1.11/xmpcore-shaded-6.1.11.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/com/mchange/mchange-commons-java/0.2.19/mchange-commons-java-0.2.19.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/com/googlecode/plist/dd-plist/1.23/dd-plist-1.23.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/gagravarr/vorbis-java-core/0.8/vorbis-java-core-0.8.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/poi/poi-ooxml/4.1.2/poi-ooxml-4.1.2.jar
  [get] To: 


setup-maven-url:

download-via-maven:
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/poi/poi-ooxml-schemas/4.1.2/poi-ooxml-schemas-4.1.2.jar
  [get] To: 

Build failed in Jenkins: ManifoldCF » ManifoldCF-mvn #88

2023-10-09 Thread Apache Jenkins Server
See 


Changes:

[Karl Wright] Restore native2ascii invocation

[Karl Wright] Prepare trunk for 2.27 development

[Karl Wright] Tie off release 2.26


--
[...truncated 476.14 KB...]
AU
site/src/documentation/resources/images/zh_CN/list-authority-connections.PNG
AU
site/src/documentation/resources/images/zh_CN/list-authority-groups.PNG
AUsite/src/documentation/resources/images/zh_CN/list-jobs.PNG
AU
site/src/documentation/resources/images/zh_CN/list-mapping-connections.PNG
AU
site/src/documentation/resources/images/zh_CN/list-output-connections.PNG
AU
site/src/documentation/resources/images/zh_CN/list-repository-connections.PNG
AU
site/src/documentation/resources/images/zh_CN/list-transformation-connections.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-authority-cache.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-authority-server.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-authority-status.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-authority-user-mapping.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-connection-document-access.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-connection-document-view.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-connection-server.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-connection-status.PNG
AUsite/src/documentation/resources/images/zh_CN/livelink-job-filters.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-job-metadata.PNG
AUsite/src/documentation/resources/images/zh_CN/livelink-job-paths.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-job-security.PNG
AUsite/src/documentation/resources/images/zh_CN/login.PNG
AU
site/src/documentation/resources/images/zh_CN/mapping-prerequisites.PNG
AUsite/src/documentation/resources/images/zh_CN/mapping-throttling.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-authority-memex-server.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-authority-status.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-authority-user-mapping.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-connection-memex-server.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-connection-status.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-connection-web-server.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-credentials.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-document-server.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-records-server.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-status.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-user-service-server.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-credentials.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-document-server.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-records-server.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-status.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-web-client.PNG
AU
site/src/documentation/resources/images/zh_CN/metadataadjuster-job-add-metadata.PNG
AU
site/src/documentation/resources/images/zh_CN/metadataadjuster-job-move-metadata.PNG
AU
site/src/documentation/resources/images/zh_CN/opensearchserver-connection-parameters.PNG
AU
site/src/documentation/resources/images/zh_CN/opensearchserver-history-report.PNG
AU
site/src/documentation/resources/images/zh_CN/opensearchserver-job-parameters.PNG
AU
site/src/documentation/resources/images/zh_CN/opensearchserver-user.PNG
AUsite/src/documentation/resources/images/zh_CN/output-throttling.PNG
AUsite/src/documentation/resources/images/zh_CN/queue-status-example.PNG
AU
site/src/documentation/resources/images/zh_CN/queue-status-select-connection.PNG
AU
site/src/documentation/resources/images/zh_CN/queue-status-select-job.PNG
AU
site/src/documentation/resources/images/zh_CN/regexp-mapping-status.PNG
AU
site/src/documentation/resources/images/zh_CN/regexp-mapping-user-mapping.PNG
AU
site/src/documentation/resources/images/zh_CN/repository-throttling-with-throttle.PNG
AU
site/src/documentation/resources/images/zh_CN/repository-throttling.PNG
AU
site/src/documentation/resources/images/zh_CN/rss-configure-bandwidth.PNG
AU

Propose adding "User-Agent platform" option for crawling mobile sites

2023-10-09 Thread Mingchun Zhao
Hi all,

Allow me to propose a new feature for crawling mobile sites that restrict
access to content based on User-Agent header.
Actually, Our customer's mobile website was failing to crawl because access
was restricted based on whether the User-Agent request header is related to
the mobile platform.
For this reason, we added the "User-Agent platform" option to the new
"Request Headers" tab on the web repository connector page so that this
mobile website doesn't fail to crawl.

I've created a jira issue and PR if you are interested:
https://issues.apache.org/jira/projects/CONNECTORS/issues/CONNECTORS-1748
https://github.com/apache/manifoldcf/pull/153

Kind regards,
Mingchun


Re: Ready for the 2.26 release?

2023-10-09 Thread Mingchun Zhao
Hi Karl, Olivier, Guylaine,

> It looks like the native2ascii invocations have been stripped entirely
from
the build.xml files everywhere, not just in ui-core.

FYI, the native2ascii command disappeared in the patch I provided to
support Java 11 which was included in the PR below. I'm so sorry for that.
https://github.com/apache/manifoldcf/pull/150/files#diff-38e7ea3183260ebac5d6772723b64a3b69ce8aab6a0c1ca2ada6fd9f410c0ba6L283

Thank you for investigating this matter!

Regards,
Mingchun

2023年10月10日(火) 2:17 Karl Wright :

> It's worse than that.
> It looks like the native2ascii invocations have been stripped entirely from
> the build.xml files everywhere, not just in ui-core.  I'm trying to figure
> out when that happened and see if I can get it back.
>
> Karl
>
>
> On Mon, Oct 9, 2023 at 12:42 PM Olivier Tavard <
> olivier.tav...@francelabs.com> wrote:
>
> > Hi Karl,
> >
> > My colleague Guylaine noticed that one line was missing into
> > framework/build.xml into the latest version :
> >  > dest="build/ui-core/classes" includes="**/*.properties" />
> >
> > So all the i18n translation files were missing into the build. The
> correct
> > code is :
> >
> > 
> > 
> >  > destdir="build/ui-core/classes" deprecation="true" target="1.8"
> > source="1.8" debug="true" encoding="utf-8"
> debuglevel="lines,vars,source">
> > 
> > 
> > 
> > 
> > 
> >   *   > src="ui-core/src/main/native2ascii" dest="build/ui-core/classes"
> > includes="**/*.properties" />*
> > 
> >
> > By adding this line, the build  is now OK. We can do a PR tomorrow for
> > that if needed.
> >
> > Thanks,
> >
> >
> > Olivier TAVARD
> > Directeur Général - Cofondateur
> > France Labs – Makers of Datafari Enteprise Search
> > Datafari Enterprise Search 
> > 
> >
> > [image:
> > image003.jpg]
> >
> > Le 9 oct. 2023 à 18:32, Karl Wright  a écrit :
> >
> > I looked very briefly at this and discovered that every message is
> > affected.
> > It may be due, therefore, to jetty refusing access to the translation
> > resources.  But if that's the case I'm not going to be able to do
> anything
> > to get this release out this month; I'm booked solid in fact until
> January.
> >
> > So good luck, folks.  I'd try rolling the Jetty version update back if
> you
> > can as a first step.
> >
> > Karl
> >
> >
> > On Mon, Oct 9, 2023 at 9:08 AM Karl Wright  wrote:
> >
> > No change to paths has been made.
> > Probably the translation files have been corrupted due to many merges and
> > perhaps bad encodings for some of them.  It will need to be looked into.
> > Karl
> >
> >
> > On Mon, Oct 9, 2023 at 8:40 AM Guylaine BASSETTE <
> > guylaine.basse...@francelabs.com> wrote:
> >
> > Hello all,
> >
> > We have tested this version and everything is OK, except for translation,
> > something is broken:
> >
> > It looks like the translations files are not found anymore. Maybe a
> > change in the path to those files ?
> > Best regards,
> > Guylaine
> >
> > France Labs – Your knowledge, now
> > Datafari Enterprise Search – Découvrez la version 5 / Discover our
> > version 5
> > www.datafari.com
> >
> > Retrouvez-nous à Milipol  du 14 au 17 novembre
> >
> > Le 06/10/2023 à 09:31, Karl Wright a écrit :
> >
> > Hi all,
> >
> > The tentative release schedule had a release going out on Sept 30th,
> which
> > is now overdue.  Partly this was because of me, but also partly it's the
> > result of new contributions from France Labs.  But these contributions
> are
> > now committed to trunk and we could go ahead - unless others are expected
> > to be coming shortly, in which case we should wait.  Please let me know.
> >
> > In any case, if I don't hear back by this weekend I will try to create a
> > release candidate then.
> >
> > Karl
> >
> >
> >
>


Re: Ready for the 2.26 release?

2023-10-09 Thread Karl Wright
It's worse than that.
It looks like the native2ascii invocations have been stripped entirely from
the build.xml files everywhere, not just in ui-core.  I'm trying to figure
out when that happened and see if I can get it back.

Karl


On Mon, Oct 9, 2023 at 12:42 PM Olivier Tavard <
olivier.tav...@francelabs.com> wrote:

> Hi Karl,
>
> My colleague Guylaine noticed that one line was missing into
> framework/build.xml into the latest version :
>  dest="build/ui-core/classes" includes="**/*.properties" />
>
> So all the i18n translation files were missing into the build. The correct
> code is :
>
> 
> 
>  destdir="build/ui-core/classes" deprecation="true" target="1.8"
> source="1.8" debug="true" encoding="utf-8" debuglevel="lines,vars,source">
> 
> 
> 
> 
> 
>   *   src="ui-core/src/main/native2ascii" dest="build/ui-core/classes"
> includes="**/*.properties" />*
> 
>
> By adding this line, the build  is now OK. We can do a PR tomorrow for
> that if needed.
>
> Thanks,
>
>
> Olivier TAVARD
> Directeur Général - Cofondateur
> France Labs – Makers of Datafari Enteprise Search
> Datafari Enterprise Search 
> 
>
> [image:
> image003.jpg]
>
> Le 9 oct. 2023 à 18:32, Karl Wright  a écrit :
>
> I looked very briefly at this and discovered that every message is
> affected.
> It may be due, therefore, to jetty refusing access to the translation
> resources.  But if that's the case I'm not going to be able to do anything
> to get this release out this month; I'm booked solid in fact until January.
>
> So good luck, folks.  I'd try rolling the Jetty version update back if you
> can as a first step.
>
> Karl
>
>
> On Mon, Oct 9, 2023 at 9:08 AM Karl Wright  wrote:
>
> No change to paths has been made.
> Probably the translation files have been corrupted due to many merges and
> perhaps bad encodings for some of them.  It will need to be looked into.
> Karl
>
>
> On Mon, Oct 9, 2023 at 8:40 AM Guylaine BASSETTE <
> guylaine.basse...@francelabs.com> wrote:
>
> Hello all,
>
> We have tested this version and everything is OK, except for translation,
> something is broken:
>
> It looks like the translations files are not found anymore. Maybe a
> change in the path to those files ?
> Best regards,
> Guylaine
>
> France Labs – Your knowledge, now
> Datafari Enterprise Search – Découvrez la version 5 / Discover our
> version 5
> www.datafari.com
>
> Retrouvez-nous à Milipol  du 14 au 17 novembre
>
> Le 06/10/2023 à 09:31, Karl Wright a écrit :
>
> Hi all,
>
> The tentative release schedule had a release going out on Sept 30th, which
> is now overdue.  Partly this was because of me, but also partly it's the
> result of new contributions from France Labs.  But these contributions are
> now committed to trunk and we could go ahead - unless others are expected
> to be coming shortly, in which case we should wait.  Please let me know.
>
> In any case, if I don't hear back by this weekend I will try to create a
> release candidate then.
>
> Karl
>
>
>


Re: Ready for the 2.26 release?

2023-10-09 Thread Olivier Tavard
Hi Karl,

My colleague Guylaine noticed that one line was missing into 
framework/build.xml into the latest version :


So all the i18n translation files were missing into the build. The correct code 
is :












By adding this line, the build  is now OK. We can do a PR tomorrow for that if 
needed.

Thanks,


Olivier TAVARD
Directeur Général - Cofondateur
France Labs – Makers of Datafari Enteprise Search
Datafari Enterprise Search


[image003.jpg]

Le 9 oct. 2023 à 18:32, Karl Wright  a écrit :

I looked very briefly at this and discovered that every message is affected.
It may be due, therefore, to jetty refusing access to the translation
resources.  But if that's the case I'm not going to be able to do anything
to get this release out this month; I'm booked solid in fact until January.

So good luck, folks.  I'd try rolling the Jetty version update back if you
can as a first step.

Karl


On Mon, Oct 9, 2023 at 9:08 AM Karl Wright 
mailto:daddy...@gmail.com>> wrote:

No change to paths has been made.
Probably the translation files have been corrupted due to many merges and
perhaps bad encodings for some of them.  It will need to be looked into.
Karl


On Mon, Oct 9, 2023 at 8:40 AM Guylaine BASSETTE <
guylaine.basse...@francelabs.com> wrote:

Hello all,

We have tested this version and everything is OK, except for translation,
something is broken:

It looks like the translations files are not found anymore. Maybe a
change in the path to those files ?
Best regards,
Guylaine

France Labs – Your knowledge, now
Datafari Enterprise Search – Découvrez la version 5 / Discover our
version 5
www.datafari.com

Retrouvez-nous à Milipol  du 14 au 17 novembre

Le 06/10/2023 à 09:31, Karl Wright a écrit :

Hi all,

The tentative release schedule had a release going out on Sept 30th, which
is now overdue.  Partly this was because of me, but also partly it's the
result of new contributions from France Labs.  But these contributions are
now committed to trunk and we could go ahead - unless others are expected
to be coming shortly, in which case we should wait.  Please let me know.

In any case, if I don't hear back by this weekend I will try to create a
release candidate then.

Karl



Re: Ready for the 2.26 release?

2023-10-09 Thread Karl Wright
I looked very briefly at this and discovered that every message is affected.
It may be due, therefore, to jetty refusing access to the translation
resources.  But if that's the case I'm not going to be able to do anything
to get this release out this month; I'm booked solid in fact until January.

So good luck, folks.  I'd try rolling the Jetty version update back if you
can as a first step.

Karl


On Mon, Oct 9, 2023 at 9:08 AM Karl Wright  wrote:

> No change to paths has been made.
> Probably the translation files have been corrupted due to many merges and
> perhaps bad encodings for some of them.  It will need to be looked into.
> Karl
>
>
> On Mon, Oct 9, 2023 at 8:40 AM Guylaine BASSETTE <
> guylaine.basse...@francelabs.com> wrote:
>
>> Hello all,
>>
>> We have tested this version and everything is OK, except for translation,
>> something is broken:
>>
>> It looks like the translations files are not found anymore. Maybe a
>> change in the path to those files ?
>> Best regards,
>> Guylaine
>>
>> France Labs – Your knowledge, now
>> Datafari Enterprise Search – Découvrez la version 5 / Discover our
>> version 5
>> www.datafari.com
>>
>> Retrouvez-nous à Milipol  du 14 au 17 novembre
>>
>> Le 06/10/2023 à 09:31, Karl Wright a écrit :
>>
>> Hi all,
>>
>> The tentative release schedule had a release going out on Sept 30th, which
>> is now overdue.  Partly this was because of me, but also partly it's the
>> result of new contributions from France Labs.  But these contributions are
>> now committed to trunk and we could go ahead - unless others are expected
>> to be coming shortly, in which case we should wait.  Please let me know.
>>
>> In any case, if I don't hear back by this weekend I will try to create a
>> release candidate then.
>>
>> Karl
>>
>>
>>


[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector

2023-10-09 Thread Julien Massiera (Jira)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773278#comment-17773278
 ] 

Julien Massiera commented on CONNECTORS-1740:
-

Bonjour,
Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et 
cet email sera bientot desactive. Pour toute question sur France Labs ou sur 
des projets en cours, merci de contacter cedric.ulmer att francelabs.com


> Solr 9 output connector
> ---
>
> Key: CONNECTORS-1740
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1740
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.23
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Attachments: CONNECTORS-1740.patch
>
>
> The current Solr output connector is not compatible with Solr 9.x
> We need to update the connector with SolrJ 9 and make sure that the custom 
> code (multipart post requests, basic/preemptive auth) is still required, and, 
> in case it is, port it ! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector

2023-10-09 Thread Guylaine Bassette (Jira)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773277#comment-17773277
 ] 

Guylaine Bassette commented on CONNECTORS-1740:
---

Hello [~kwri...@metacarta.com],

Thanks to have merged my Zookeeper fix !

We have tested it in our application and everything works well: job 
configuration and Solr indexation.

> Solr 9 output connector
> ---
>
> Key: CONNECTORS-1740
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1740
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.23
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Attachments: CONNECTORS-1740.patch
>
>
> The current Solr output connector is not compatible with Solr 9.x
> We need to update the connector with SolrJ 9 and make sure that the custom 
> code (multipart post requests, basic/preemptive auth) is still required, and, 
> in case it is, port it ! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector

2023-10-09 Thread Julien Massiera (Jira)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773268#comment-17773268
 ] 

Julien Massiera commented on CONNECTORS-1740:
-

Bonjour,
Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et 
cet email sera bientot desactive. Pour toute question sur France Labs ou sur 
des projets en cours, merci de contacter cedric.ulmer att francelabs.com


> Solr 9 output connector
> ---
>
> Key: CONNECTORS-1740
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1740
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.23
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Attachments: CONNECTORS-1740.patch
>
>
> The current Solr output connector is not compatible with Solr 9.x
> We need to update the connector with SolrJ 9 and make sure that the custom 
> code (multipart post requests, basic/preemptive auth) is still required, and, 
> in case it is, port it ! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector

2023-10-09 Thread Guylaine Bassette (Jira)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773266#comment-17773266
 ] 

Guylaine Bassette commented on CONNECTORS-1740:
---

Hello [~mingchun.zhao],

Thanks for your contribution with Java 11 ! (y)

I have integrated your patch with my contribution to fix the Zookeeper bug (PR 
150, al ready merged to the master Branch).

> Solr 9 output connector
> ---
>
> Key: CONNECTORS-1740
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1740
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.23
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Attachments: CONNECTORS-1740.patch
>
>
> The current Solr output connector is not compatible with Solr 9.x
> We need to update the connector with SolrJ 9 and make sure that the custom 
> code (multipart post requests, basic/preemptive auth) is still required, and, 
> in case it is, port it ! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)