Re: [VOTE] Release Apache ManifoldCF 2.26, RC1

[Furkan KAMACI]

+1

On Sun, Oct 29, 2023 at 2:00 AM Mingchun Zhao 
wrote:

> +1
>
> Built and tested from tag release-2.26-RC1
>  with
> Ant.
>
> OS name: macOS 14.0
> Apache Ant(TM) version 1.10.0
> Java version: openjdk version "11.0.11"
> locale: en_US.UTF-8
>
> Thanks for doing the release!
>
> Regards,
> Mingchun
>
> 2023年10月29日(日) 1:12 Karl Wright :
>
> > Please vote on whether to release Apache ManifoldCF 2.26, RC1.  The
> release
> > candidate can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26
> >
> > There is also a release tag at:
> >
> > https//svn.apache.org/repos/asf/manifoldcf/tags/release-2.26-RC1
> >
> > Thanks to Mingchun Zhao and Guylaine Bassette for making this release
> > possible!
> >
> > Karl
> >
>

Re: [VOTE] Release ManifoldCF 2.26, RC0

[Furkan KAMACI]

Hi,

+1!

Kind regards,
Furkan Kamaci

On Wed, Oct 11, 2023 at 11:13 PM Mingchun Zhao 
wrote:

> Hi,
> Ran all the tests.
> +1 from me.
>
> Kind regards,
> Mingchun
>
> 2023年10月12日(木) 4:29 Cihad Guzel :
>
> > Hi,
> >
> > +1 from me
> >
> > Regards,
> > Cihad Guzel
> >
> > 11 Eki 2023 Çar, saat 15:08 tarihinde Karl Wright 
> > şunu
> > yazdı:
> >
> > > Please vote on whether to release Apache ManifoldCF 2.26, RC0.
> > > This release is the first release that requires at least Java 11, and
> it
> > > also includes a new CSV connector along with support for Solr 9.  The
> > > release artifact can be found at:
> > >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26
> > ,
> > > and there is a release tag also at
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.26-RC0 .
> > >
> > > Karl
> > >
> >
>

Re: Contribution : new Connector CSV

[Furkan KAMACI]

Thanks for your effort Guylaine!

On 3 Oct 2023 Tue at 12:11 Guylaine BASSETTE <
guylaine.basse...@francelabs.com> wrote:

> Hello all,
>
> In order to remove the dependency towards the JDBC CSV driver (it does
> not seem to be maintained anymore), we have refactored the CSV connector
> to make it work independently from it. Can we propose you the
> corresponding patch ? The documentation is there :
>
> https://datafari.atlassian.net/wiki/spaces/DATAFARI/pages/2894036993/CSV+Connector
>
> I have prepared a PR if you are interested:
> https://github.com/apache/manifoldcf/pull/152
>
> --
>
> Best regards,
> Guylaine
>
> France Labs – Your knowledge, now
> Datafari Enterprise Search – Découvrez la version 5 / Discover our version
> 5
> www.datafari.com 
>
>

Re: Contribution to ManifoldCF webcrawler

[Furkan KAMACI]

Hi Emeric,

First of all, thank you for your effort and suggestion. Do you have a Pull
Request for that improvement?

Kind regards,
Furkan Kamaci

On Mon, Sep 25, 2023 at 10:23 AM Emeric Bernet-Rollande <
emeric.ber...@francelabs.com> wrote:

> Hi Karl and all !
>
>
>
> I’ve been working on the MCF webcrawler component for our Datafari
> project, and I made some developments that might interest the MCF community.
>
>
>
> Currently if a website redirects the user with a code 301 or 302 and the
> « limit to seed is checked », the website (the one pointed by the
> redirection) won’t be indexed. We added an option  « Force the inclusion
> of redirections », which will override the previous checkbox if the crawl
> encounters a redirection.
>
>
>
>
>
> Would you be interested in getting the patch to integrate it into
> ManifoldCF? The corresponding documentation can be found here:
> https://datafari.atlassian.net/wiki/spaces/DATAFARI/pages/1886879745/Web+Connectors
>
>
>
> Regards,
>
>
>
> Emeric Bernet-Rollande
>
>
>
> *France Labs – Your knowledge, now*
>
> Datafari Enterprise Search – Découvrez la version 5 / Discover our version
> 5
> www.datafari.com
>
>
>

Re: [VOTE] Release ManifoldCF 2.25, RC0

[Furkan KAMACI]

+1

On Tue, May 30, 2023 at 12:20 AM Cihad Guzel  wrote:

> +1
>
> 30 May 2023 Sal, saat 00:08 tarihinde Karl Wright 
> şunu
> yazdı:
>
> > Please vote on whether to release ManifoldCF 2.25, RC0.
> >
> > This release contains one new feature: the ability to disable hopcount
> > tracking entirely, for better performance of the web connector.  The
> > attempt to update the Solr connector to release 9.x of Solr did NOT make
> it
> > in because that version of SolrJ depends on a broken version of
> zookeeper,
> > our thread coordination library.
> >
> > A release artifact can be found here:
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.25
> >
> > A release tag can also be found at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.25-RC0 .
> >
> > Karl
> >
> --
> Cihad Güzel
>

Re: [VOTE] Release Apache ManifoldCF 2.24, RC0

[Furkan KAMACI]

Hi,

+1!

Kind Regards,
Furkan KAMACI

On Wed, Nov 30, 2022 at 6:11 PM Piergiorgio Lucidi 
wrote:

> Ran all the tests.
>
> +1 from me
>
> Cheers,
> PJ
>
> Il giorno mer 30 nov 2022 alle ore 13:27 Karl Wright 
> ha scritto:
>
> > Please vote on whether to release Apache ManifoldCF 2.24, RC0.  The
> release
> > artifact can be found at:
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.24
> .
> > There is also a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.24-RC0 .
> >
> > This release contains a number of fixes for issues found externally, some
> > of them high priority.  We have therefore chosen to accelerate the
> release
> > schedule, since it was originally scheduled for the end of December.  You
> > can review CHANGES.txt for a partial list of the changes.
> >
> > Thanks,
> > Karl
> >
>
>
> --
> Piergiorgio
>

Re: [VOTE] Release Apache ManifoldCF Plugin for Solr 9.x 2.2, RC0

[Furkan KAMACI]

Hi,

+1 (binding)!

Kind Regards,
Furkan KAMACI

On Wed, Sep 7, 2022 at 2:14 PM Karl Wright  wrote:

> I need one more vote.  Anyone around?
>
> Karl
>
>
> On Mon, Sep 5, 2022 at 10:10 AM Julien Massiera <
> julien.massi...@francelabs.com> wrote:
>
> > Hi,
> >
> > Tests ok, +1
> >
> > Julien
> >
> > -Message d'origine-
> > De : Karl Wright 
> > Envoyé : dimanche 4 septembre 2022 08:12
> > À : dev 
> > Objet : [VOTE] Release Apache ManifoldCF Plugin for Solr 9.x 2.2, RC0
> >
> > Please vote whether to release the first version of the Apache ManifoldCF
> > Plugin for Solr 9.x (version 2.2, RC0).
> >
> > The release artifact can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-solr-9.x-plugin-2.2
> > .
> >
> > There is also a release tag at:
> >
> >
> https://svn.apache.org/repos/asf/manifoldcf/integration/solr-9.x/tags/release-2.2-RC0
> > .
> >
> > Karl
> >
> >
>

Re: [RESULT] [VOTE] Release Apache ManifoldCF 2.22.1, RC1

[Furkan KAMACI]

Hi,

+1 from me (binding).

I checked:

- LICENSE is fine
- NOTICE year should be fixed (I can make a commit for it)
- No unexpected binary files
- Checked PGP signatures
- Checked checksums
- Code compiles and tests successfully run

By the way, did 72 hours pass or not?

Kind Regards,
Furkan KAMACI

On Thu, May 12, 2022 at 12:05 PM Karl Wright  wrote:

> Three +1s, >72 hours.  Vote passes.
>
> Karl
>
>
> On Thu, May 12, 2022 at 3:22 AM Piergiorgio Lucidi  >
> wrote:
>
> > Tests pass also for me, a big +1 from me!
> >
> > Cheers,
> > PJ
> >
> > Il giorno mar 10 mag 2022 alle ore 11:41 Karl Wright  >
> > ha scritto:
> >
> > > Tests pass for me. +1
> > >
> > > Karl
> > >
> > >
> > > On Tue, May 10, 2022 at 5:34 AM Julien Massiera <
> > > julien.massi...@francelabs.com> wrote:
> > >
> > > > All tests ok + manual UI test ok. +1
> > > >
> > > > Julien
> > > >
> > > > -Message d'origine-
> > > > De : Karl Wright 
> > > > Envoyé : mardi 10 mai 2022 03:19
> > > > À : dev 
> > > > Objet : [VOTE] Release Apache ManifoldCF 2.22.1, RC1
> > > >
> > > > Please vote on whether to release Apache ManifoldCF 2.22.1, RC1.  The
> > > > release artifact can be found at
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.22.1
> > > > .
> > > > There is also a release tag at
> > > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.22.1-RC1.
> > > >
> > > > This patch release fixes two problems in 2.22: (1) the new LDAP
> mapper
> > > had
> > > > the same name as the Regexp mapper, which caused a unique index
> > > constraint
> > > > violation, and (2) there were conflicting versions of Apache Velocity
> > > > installed, which meant that template resolution failed in some cases.
> > > >
> > > > Further changes included fixing the Maven build to add missing
> > > > dependencies.
> > > >
> > > > Thanks,
> > > > Karl
> > > >
> > > >
> > >
> >
> >
> > --
> > Piergiorgio
> >
>

Re: Docker support and ManifoldCF SDK

[Furkan KAMACI]

Hi Piergiorgio,

Is there any link to check the source code of the current status?

Kind Regards,
Furkan KAMACI

On Thu, May 5, 2022 at 12:01 AM Markus Schuch  wrote:

> Hi PJ,
>
> If the SDK project has a dependency on the Sources ZIP file, then it
> also seems more natural to me to set up the SDK project as a separate
> repository.
>
> A standalone repository would also have the advantage that we don't make
> the module structure and the build in the trunk even more complex and
> bloatet further. And it is also easier for us to introduce modern
> tooling without being slowed down by the legacy in the the main repository.
>
> It might even be our ticket to gaining a foothold in git.
>
> Cheers,
> Markus
>
>
> Am 04.05.2022 um 13:29 schrieb Piergiorgio Lucidi:
> > Hi folks,
> >
> > I added an initial Docker support in the branch CONNECTORS-1492 and I
> have
> > also created a new issue related to the ManifoldCF SDK:
> >
> https://issues.apache.org/jira/projects/CONNECTORS/issues/CONNECTORS-1706
> >
> > The current status of this new project is described in the issue,
> > practically it works correctly, we only need to provide some examples of
> > each type of connector.
> > So I'm wondering where we could host this new project.
> >
> > Should we put the code in the main trunk?
> > In this case I could continue to work on the branch CONNECTORS-1492
> > creating a new folder in the root of the project with the sdk.
> > I have to confess that following this way it sounds strange to me because
> > the sdk is referring to the source code downloading it during the
> > initialization process.
> >
> > Or should we create a separate project for this sdk?
> > It sounds better to me this approach but I would like to receive your
> > feedback.
> >
> > Please let me know.
> > Thanks.
> >
> > Cheers,
> > PJ
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.22, RC1

[Furkan KAMACI]

Hi,

Can we use http://downloads.mongodb.org/osx/mongodb-osx-x86_64-2.6.8.tgz
from here: https://www.mongodb.org/dl/osx

Kind Regards,
Furkan KAMACI

On Sun, Apr 24, 2022 at 12:22 PM Karl Wright  wrote:

> It looks like they've locked it down.
> We really don't have a choice other than to disable the test I fear.  Have
> you been able to find an alternate URL?
>
> Karl
>
>
> On Fri, Apr 22, 2022 at 9:50 AM Piergiorgio Lucidi  >
> wrote:
>
> > Hi Karl,
> >
> > I ran ant test command and now I have a problem with
> > MongoDBOutputConnector:
> >
> > [junit] java.io.IOException: Could not open inputStream for
> > https://fastdl.mongodb.org/osx/mongodb-osx-i386-2.6.8.tgz
> >
> > Maybe MongoDB has changed this URL?
> > I'm investigating...
> >
> > Below all the exception returned by Ant
> >
> > run-IT-HSQLDB:
> > [junit] Testsuite:
> > org.apache.manifoldcf.agents.output.mongodboutput.tests.APISanityHSQLDBIT
> > [junit] Configuration file successfully read
> > [junit] [main] INFO org.eclipse.jetty.util.log - Logging initialized
> > @941ms to org.eclipse.jetty.util.log.Slf4jLog
> > [junit] [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
> > [junit] [main] INFO org.eclipse.jetty.server.session -
> > DefaultSessionIdManager workerName=node0
> > [junit] [main] INFO org.eclipse.jetty.server.session - No
> > SessionScavenger set, using defaults
> > [junit] [main] INFO org.eclipse.jetty.server.session - node0
> Scavenging
> > every 66ms
> > [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> > Started o.e.j.w.WebAppContext@4482469c{ManifoldCF Crawler
> >
> >
> Interface,/mcf-crawler-ui,file:///private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-8346-mcf-crawler-ui_war-_mcf-crawler-ui-any-2356674270627149959.dir/webapp/,AVAILABLE}{/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/dist/web/war/mcf-crawler-ui.war}
> > [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> > Started o.e.j.w.WebAppContext@3703bf3c{ManifoldCF Authorities API
> >
> >
> Webapp,/mcf-authority-service,file:///private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-8346-mcf-authority-service_war-_mcf-authority-service-any-11820210731741565141.dir/webapp/,AVAILABLE}{/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/dist/web/war/mcf-authority-service.war}
> > [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
> > Started o.e.j.w.WebAppContext@34cf5a97{ManifoldCF General API
> >
> >
> Webapp,/mcf-api-service,file:///private/var/folders/g1/vlf2szxj7tbbgm92n39l8kj8gn/T/jetty-0_0_0_0-8346-mcf-api-service_war-_mcf-api-service-any-6023197707410686222.dir/webapp/,AVAILABLE}{/Users/pjlucidi/Downloads/apache-manifoldcf-2.22/dist/web/war/mcf-api-service.war}
> > [junit] [main] INFO org.eclipse.jetty.server.AbstractConnector -
> > Started ServerConnector@6dc1484{HTTP/1.1,[http/1.1]}{0.0.0.0:8346}
> > [junit] [main] INFO org.eclipse.jetty.server.Server - Started @1817ms
> > [junit] Download Version{2.6.8}:OS_X:B32 START
> > [junit] [main] ERROR de.flapdoodle.embed.process.runtime.Starter -
> > prepare executable
> > [junit] java.io.IOException: Could not open inputStream for
> > https://fastdl.mongodb.org/osx/mongodb-osx-i386-2.6.8.tgz
> > [junit] at
> >
> >
> de.flapdoodle.embed.process.store.Downloader.downloadInputStream(Downloader.java:131)
> > [junit] at
> > de.flapdoodle.embed.process.store.Downloader.download(Downloader.java:69)
> > [junit] at
> >
> >
> de.flapdoodle.embed.process.store.ArtifactStore.checkDistribution(ArtifactStore.java:66)
> > [junit] at
> >
> >
> de.flapdoodle.embed.process.store.ExtractedArtifactStore.checkDistribution(ExtractedArtifactStore.java:60)
> > [junit] at
> > de.flapdoodle.embed.process.runtime.Starter.prepare(Starter.java:56)
> > [junit] at
> > de.flapdoodle.embed.process.runtime.Starter.prepare(Starter.java:49)
> > [junit] at
> >
> >
> org.apache.manifoldcf.agents.output.mongodboutput.tests.BaseITHSQLDB.setUpMongoDB(BaseITHSQLDB.java:69)
> > [junit] at
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > [junit] at
> >
> >
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > [junit] at
> >
> >
> java.ba

Re: [VOTE] Release Apache ManifoldCF 2.19, RC0

[Furkan KAMACI]

Hi,

+1!

Kind Regards,
Furkan KAMACI

On Mon, May 3, 2021 at 9:49 PM Cihad Guzel  wrote:

> Hi,
>
> +1 from me
>
> Cihad Güzel
>
>
>  adresine sahip kullanıcı 3 May 2021 Pzt,
> 16:39 tarihinde şunu yazdı:
>
> > Hi,
> >
> > On our side, we plan to test this release on Thursday. I'll give my vote
> > after the test if it will not be too late
> >
> > Julien
> >
> > -Message d'origine-
> > De : Karl Wright 
> > Envoyé : lundi 3 mai 2021 13:43
> > À : dev 
> > Objet : Re: [VOTE] Release Apache ManifoldCF 2.19, RC0
> >
> > Reminder: Voting underway.  Please evaluate and vote.
> >
> > Ran tests.  +1 from me.
> >
> > Karl
> >
> >
> > On Wed, Apr 28, 2021 at 7:21 PM Karl Wright  wrote:
> >
> > > Please vote to release Apache ManifoldCF 2.19, RC0.  The release
> > > artifact can be found at:
> > > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.
> > > 19
> > > .  There is also a release tag at
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.19-RC0 .
> > >
> > > This release has a significant update to the Elastic Search connector,
> > > to both bring it up to date, and to work around the problem with
> > > limited ID length that ES has.
> > >
> > > Karl
> > >
> > >
> >
> >
>

Re: GSOC - Mavenisation of MCF ?

[Furkan KAMACI]

Hi Karl,

We don't have a MongoDB repository connector. We have a MongoDB output
connector?

Kind Regards,
Furkan KAMACI

On Wed, Feb 10, 2021 at 3:47 PM Karl Wright  wrote:

> Hi Furkan,
>
> There is already a mongoDB connector:
>
> 12/12/2020  03:51 AM  mongodb
>
>
>
> On Wed, Feb 10, 2021 at 4:10 AM Furkan KAMACI 
> wrote:
>
> > Hi,
> >
> > It could be nice to have a connector for a GSoC task i.e. a MongoDB
> > repository connector.
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Tue, Feb 9, 2021 at 10:48 PM Cedric Ulmer <
> cedric.ul...@francelabs.com>
> > wrote:
> >
> > > Hi Karl and Piergiorgio,
> > >
> > > Ok got it, was a bad idea!
> > > Wrt connectors, not sure either, doing a good connector (incl.
> > > documentation) is rather time consuming, and 2 months flies very fast.
> > The
> > > best a student could do would probably be to look at a source API and
> > > devise how to best use it to create a proper connector.
> > >
> > > Regards,
> > >
> > > Cedric
> > > CEO
> > > France Labs – Makers of Datafari Enteprise Search
> > > Vainqueur du trophée du Jury à IMAgineDAY 2021
> > >
> > >
> > > -Message d'origine-
> > > De : Piergiorgio Lucidi 
> > > Envoyé : lundi 8 février 2021 13:56
> > > À : dev 
> > > Objet : Re: GSOC - Mavenisation of MCF ?
> > >
> > > I agree with Karl,
> > > for GSoC purposes it's better to propose something related to an
> > > independent and well defined connector.
> > > PJ
> > >
> > > Il giorno lun 8 feb 2021 alle ore 12:57 Karl Wright <
> daddy...@gmail.com>
> > > ha
> > > scritto:
> > >
> > > > There are already poms throughout.  However, release distribution
> > > > structure cannot be built with Maven at this time because the
> > > > directory structure of the final release artifact is complex, and
> > > > because we want individual external connector developers to be able
> to
> > > "add into" this.
> > > >
> > > > In other words, it is far too big a project for a GSOC exercise.
> > > >
> > > > Karl
> > > >
> > > >
> > > > On Mon, Feb 8, 2021 at 6:49 AM Cedric Ulmer
> > > > 
> > > > wrote:
> > > >
> > > > > Hi Karl,
> > > > >
> > > > > With regards to the Google Summer of Code, we have a suggestion:
> > > > > would it be a good idea to propose as a subject the mavenisation of
> > > > > MCF ? If yes,
> > > > is
> > > > > it you who needs to apply since we as France Labs are not
> > > > > responsible for the Apache MCF project ? We can off course act as
> > > mentors of the student.
> > > > > Also, if Manifoldians have other ideas for the GSOC, I think it's
> > > > > time to talk about it because the deadline for organizations is
> Feb.
> > > 19th.
> > > > >
> > > > > Cedric
> > > > > CEO
> > > > > France Labs - Makers of Datafari Enteprise Search<
> > > > > https://www.datafari.com/en> Winners of the trophy of the Jury at
> > > > > IMAgineDAY<
> https://www.ima-dt.org/ima/event/detail.html/idConf/938>
> > > > > 2021
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Piergiorgio
> > >
> >
>

Re: GSOC - Mavenisation of MCF ?

[Furkan KAMACI]

Hi,

It could be nice to have a connector for a GSoC task i.e. a MongoDB
repository connector.

Kind Regards,
Furkan KAMACI

On Tue, Feb 9, 2021 at 10:48 PM Cedric Ulmer 
wrote:

> Hi Karl and Piergiorgio,
>
> Ok got it, was a bad idea!
> Wrt connectors, not sure either, doing a good connector (incl.
> documentation) is rather time consuming, and 2 months flies very fast. The
> best a student could do would probably be to look at a source API and
> devise how to best use it to create a proper connector.
>
> Regards,
>
> Cedric
> CEO
> France Labs – Makers of Datafari Enteprise Search
> Vainqueur du trophée du Jury à IMAgineDAY 2021
>
>
> -Message d'origine-
> De : Piergiorgio Lucidi 
> Envoyé : lundi 8 février 2021 13:56
> À : dev 
> Objet : Re: GSOC - Mavenisation of MCF ?
>
> I agree with Karl,
> for GSoC purposes it's better to propose something related to an
> independent and well defined connector.
> PJ
>
> Il giorno lun 8 feb 2021 alle ore 12:57 Karl Wright 
> ha
> scritto:
>
> > There are already poms throughout.  However, release distribution
> > structure cannot be built with Maven at this time because the
> > directory structure of the final release artifact is complex, and
> > because we want individual external connector developers to be able to
> "add into" this.
> >
> > In other words, it is far too big a project for a GSOC exercise.
> >
> > Karl
> >
> >
> > On Mon, Feb 8, 2021 at 6:49 AM Cedric Ulmer
> > 
> > wrote:
> >
> > > Hi Karl,
> > >
> > > With regards to the Google Summer of Code, we have a suggestion:
> > > would it be a good idea to propose as a subject the mavenisation of
> > > MCF ? If yes,
> > is
> > > it you who needs to apply since we as France Labs are not
> > > responsible for the Apache MCF project ? We can off course act as
> mentors of the student.
> > > Also, if Manifoldians have other ideas for the GSOC, I think it's
> > > time to talk about it because the deadline for organizations is Feb.
> 19th.
> > >
> > > Cedric
> > > CEO
> > > France Labs - Makers of Datafari Enteprise Search<
> > > https://www.datafari.com/en> Winners of the trophy of the Jury at
> > > IMAgineDAY< https://www.ima-dt.org/ima/event/detail.html/idConf/938>
> > > 2021
> > >
> > >
> > >
> >
>
>
> --
> Piergiorgio
>

Re: Solr ingester connector contribution

[Furkan KAMACI]

Hi Olivier,

Could you create a JIRA issue as you mentioned? You can attach your patch
or create a PR and then we can talk about it.

Kind Regards,
Furkan KAMACI

On Mon, Sep 21, 2020 at 12:33 PM Olivier Tavard <
olivier.tav...@francelabs.com> wrote:

> Hello MCF community,
>
> I contact you because we developed a new repository connector for crawling
> data from Solr and we would like to contribute to MCF by releasing the code
> into Apache v2 license.
> I can create a new ticket on Jira and attach the code on it with the
> associated documentation if you are interested.
>
> The goal of this connector is to crawl Solr instances and manage it in MCF
> rather than using DIH for instance.
> So to do it, we send requests to Solr and we manage the large number of
> results thanks to the cursormark. The Solr fields must be stored in order
> to be gathered.
>
> By the way we do not use any specific libraries, all the dependencies are
> already into MCF. We tested it so far for Solr 7 and 8 versions.
>
> Best regards,
>
> Olivier Tavard

Re: [RESULT] [VOTE] Release Apache ManifoldCF 2.17, RC1

[Furkan KAMACI]

Hi,

+1 from me too.

Kind Regards,
Furkan KAMACI

On Wed, Sep 16, 2020 at 11:31 AM Karl Wright  wrote:

> Three +1's, >>72 hours.  Vote passes, finally!
>
> Karl
>
> On Wed, Sep 16, 2020 at 1:12 AM Piergiorgio Lucidi  >
> wrote:
>
> > +1 from me.
> >
> > PJ
> >
> >
> > Il Sab 5 Set 2020, 12:32 Karl Wright  ha scritto:
> >
> > > Please vote on whether to release Apache ManifoldCF 2.17, RC1.  The
> > release
> > > artifact can be found here:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.17
> > >
> > > There is also a release tag at:
> > >
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.17-RC1
> > >
> > > This release does not contain anything major - just a few bug fixes,
> > > summarized in the CHANGES.txt file.  It does include documentation,
> > > however, which did not get successfully built for the 2.16 release.
> > Please
> > > review carefully with that in mind.
> > >
> > > The respin was required because the ElasticSearch test did not properly
> > > work on the Mac.
> > >
> > > Thanks!
> > > Karl
> > >
> >
>

Re: Release time again

[Furkan KAMACI]

Hi,

+1 from me too.

Kind Regards,
Furkan KAMACI

12 Ağu 2020 Çar, saat 00:05 tarihinde Cihad Guzel  şunu
yazdı:

> Hi Karl,
>
> +1 from me.
>
> Cihad Guzel
>
>
> Piergiorgio Lucidi , 11 Ağu 2020 Sal, 22:52
> tarihinde şunu yazdı:
>
> > Hi Karl,
> >
> > sure, +1 from me.
> >
> > PJ
> >
> >
> > Il Mar 11 Ago 2020, 14:44 Karl Wright  ha scritto:
> >
> > > Hi all,
> > > August 31 is our next scheduled release date.  The release should
> > probably
> > > go out because the documentation in the last release did not properly
> > build
> > > (since corrected, but no new artifacts have been pushed).  Other than
> > that,
> > > I can think of nothing that hints at a new release - the mailing lists
> > have
> > > been quite slow, and there are three issues in the release, that is
> all.
> > >
> > > Given that, I propose doing a patch release, not a full release.  Any
> > > objections?
> > >
> > > Karl
> > >
> >
>

SAP HANA for Support

[Furkan KAMACI]

Hi,

Does ManifoldCFsupport SAP HANA as a repository connection for crawling?
HANA supports a JDBC driver for such purposes.

On the other hand, it could be nice to learn if anybody else tried such a
thing before.

Kind Regards,
Furkan KAMACI

[jira] [Commented] (CONNECTORS-1648) PostgreSQL 10,11 and 12 support

[Furkan Kamaci (Jira)]

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

Furkan Kamaci commented on CONNECTORS-1648:
---

[~michaelcizmar] have you run any performance test regarding PostgreSQL 12 as 
like here: 
[https://manifoldcf.apache.org/release/release-2.15/en_US/how-to-build-and-deploy.html]

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Release Apache ManifoldCF 2.16, RC0

[Furkan KAMACI]

Hi,

+1 from me.

I checked:

- LICENSE is fine
- NOTICE should be updated (minor issue, I can fix it)
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
- Apache rat checks are OK


PS: I got an error while compiling and testing with Java 11 but seems to
related with my environment:

[ERROR] Failed to execute goal on project mcf-cmis-connector: Could not
resolve dependencies for project
org.apache.manifoldcf:mcf-cmis-connector:jar:2.16: Failed to collect
dependencies at
org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:1.1.0 ->
org.apache.chemistry.opencmis:chemistry-opencmis-client-bindings:jar:1.1.0
-> org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.12 ->
org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.12 ->
org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.12 ->
com.sun.xml.bind:jaxb-impl:jar:2.1.14: Failed to read artifact descriptor
for com.sun.xml.bind:jaxb-impl:jar:2.1.14: Could not transfer artifact
com.sun.xml.bind:jaxb-impl:pom:2.1.14 from/to central (
https://repo.maven.apache.org/maven2): Transfer failed for
https://repo.maven.apache.org/maven2/com/sun/xml/bind/jaxb-impl/2.1.14/jaxb-impl-2.1.14.pom:
Operation timed out (Read failed)

Kind Regards,
Furkan KAMACI

On Sun, May 3, 2020 at 9:59 PM Michael Cizmar 
wrote:

> Great work Karl!  I'm looking forward to trying this out.
>
> On Sun, May 3, 2020 at 1:31 PM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.16, RC0.  This
> > release has a new confluence connector as well as preliminary support for
> > Java 11.  The release artifact can be found at:
> >
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.16
> >
> > There is a release tag at:
> >
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.16-RC0
> >
> > Thanks in advance!
> > Karl
> >
>

Re: Release schedule

[Furkan KAMACI]

Hi,

By the way, when I check the error here:
https://issues.apache.org/jira/secure/attachment/12997363/elastic-search-1.0.1-java11-build-error.log

Seems that it is not specific to Java 11:
https://stackoverflow.com/questions/46636954/elasticsearch-1-1-2-not-starting-properly

Upgrading ES to minimum Java 9 support version which is 6.2.x can be fine:
https://www.elastic.co/de/support/matrix#matrix_jvm

Kind Regards,
Furkan KAMACI

On Sat, Apr 18, 2020 at 4:49 PM Michael Cizmar 
wrote:

> I've got a fix for this.  I switched to using a Maven plugin that spins up
> an Elasticsearch instance.  With this, you need only to remove the Node
> code in the integration tests.  Tested with 6.x client and 7.x
> elasticsearch.
>
> There are more things we can do with this output plugin in the future like
> moving to the SDK.
>
> M
>
> On 4/18/20, 8:32 AM, "Karl Wright"  wrote:
>
> Thanks for the quick reply.
> I agree we don't want to turn off the ES connector itself, but yes we
> will
> need to shut down the tests.  Cihad, would you like to propose a
> strategy
> for that?  I think for now just marking them with @Ignore should be OK,
> since the tests don't have compile time dependencies on missing
> classes.
> What do you think?
>
> Upgrading to ES 6.x is obviously the right thing to do but who here
> has the
> knowledge to do a good job with this?  I am certain there are a number
> of
> ES users lurking on this list.  Please volunteer if so.
>
> Karl
>
>
> On Sat, Apr 18, 2020 at 9:15 AM Furkan KAMACI 
> wrote:
>
> > Hi,
> >
> > There is a compatibility matrix for Elasticsearch. We need to
> support at
> > least Elasticsearch 6.5.x for Java 11 support. You can check it from
> here:
> > https://www.elastic.co/de/support/matrix#matrix_jvm
> >
> > @Cihad
> >
> > As far as I know, current support is not 2.0.0. It is 5.5.2:
> > https://github.com/apache/manifoldcf-integration-elasticsearch-5.5
> >
> > @Karl Wright 
> >
> > So, such an upgrade from 5.5.2 to 6.5.x may not be so painful.
> Committers
> > who use ES can comment on this.
> >
> > My comments:
> >
> > +1 to temporarily turning those tests off
> > -1 to temporarily turning the connector off
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Sat, Apr 18, 2020 at 3:27 PM Cihad Guzel 
> wrote:
> >
> >> Hi Karl,
> >>
> >> MFC ES Connector uses the Elastic Search 2.0.0 . It's an ancient
> version.
> >> The latest version is 7.6.2 . So, I agree with you and I think we
> can
> >> temporarily turn the connector off.
> >>
> >> +1
> >>
> >> Kind Regards,
> >> Cihad Güzel
> >>
> >>
> >> Karl Wright , 18 Nis 2020 Cmt, 11:41 tarihinde
> şunu
> >> yazdı:
> >>
> >> > Hi all,
> >> >
> >> > We're due to release ManifoldCF 2.16 by April 30th.  The major
> work for
> >> > this release was adoption of Java 11, and that work is incomplete
> >> because
> >> > of ElasticSearch incompatibilities.  I'm therefore tempted to
> hold the
> >> > release until we at least have a plan for dealing with ES going
> forward.
> >> >
> >> > It's not clear that our ES connector support is affected, but
> certainly
> >> our
> >> > integration tests are, because Java 11 isn't supported in any of
> the ES
> >> > versions we run for those tests.  So at the least we need to
> decide to
> >> turn
> >> > those off.  And indeed, we really need to have someone with ES
> >> experience
> >> > map a strategy for getting our ES support back into compliance
> with
> >> what's
> >> > out in the world at large now.  Cihad Guzel did much work on Java
> 11 but
> >> > stumbled over the Elastic Search problem.  Any of our committers
> who
> >> know
> >> > ES and are stuck inside at the moment, please speak up.
> >> >
> >> > Thanks in advance,
> >> > Karl
> >> >
> >>
> >
>
>

Re: Release schedule

[Furkan KAMACI]

Hi,

There is a compatibility matrix for Elasticsearch. We need to support at
least Elasticsearch 6.5.x for Java 11 support. You can check it from here:
https://www.elastic.co/de/support/matrix#matrix_jvm

@Cihad

As far as I know, current support is not 2.0.0. It is 5.5.2:
https://github.com/apache/manifoldcf-integration-elasticsearch-5.5

@Karl Wright 

So, such an upgrade from 5.5.2 to 6.5.x may not be so painful. Committers
who use ES can comment on this.

My comments:

+1 to temporarily turning those tests off
-1 to temporarily turning the connector off

Kind Regards,
Furkan KAMACI

On Sat, Apr 18, 2020 at 3:27 PM Cihad Guzel  wrote:

> Hi Karl,
>
> MFC ES Connector uses the Elastic Search 2.0.0 . It's an ancient version.
> The latest version is 7.6.2 . So, I agree with you and I think we can
> temporarily turn the connector off.
>
> +1
>
> Kind Regards,
> Cihad Güzel
>
>
> Karl Wright , 18 Nis 2020 Cmt, 11:41 tarihinde şunu
> yazdı:
>
> > Hi all,
> >
> > We're due to release ManifoldCF 2.16 by April 30th.  The major work for
> > this release was adoption of Java 11, and that work is incomplete because
> > of ElasticSearch incompatibilities.  I'm therefore tempted to hold the
> > release until we at least have a plan for dealing with ES going forward.
> >
> > It's not clear that our ES connector support is affected, but certainly
> our
> > integration tests are, because Java 11 isn't supported in any of the ES
> > versions we run for those tests.  So at the least we need to decide to
> turn
> > those off.  And indeed, we really need to have someone with ES experience
> > map a strategy for getting our ES support back into compliance with
> what's
> > out in the world at large now.  Cihad Guzel did much work on Java 11 but
> > stumbled over the Elastic Search problem.  Any of our committers who know
> > ES and are stuck inside at the moment, please speak up.
> >
> > Thanks in advance,
> > Karl
> >
>

MongoDB Connector

[Furkan KAMACI]

Hi All,

Is there anybody who works on developing a MongoDB connector to fetch data
(not an output connector)?

Kind Regards,
Furkan KAMACI

Re: [VOTE] Release Apache ManifoldCF 2.15, RC0

[Furkan KAMACI]

Hi,

+1

Kind Regards,
Furkan KAMACI

25 Ara 2019 Çar, saat 02:06 tarihinde Cihad Guzel  şunu
yazdı:

> Hi,
>
> +1 from me. Ran all tests.
>
> Regards,
> Cihad Guzel
>
>
> Karl Wright , 24 Ara 2019 Sal, 17:34 tarihinde şunu
> yazdı:
>
> > Ran all tests.
> >
> > +1 from me.
> >
> > Karl
> >
> >
> > On Sun, Dec 22, 2019 at 7:13 PM Karl Wright  wrote:
> >
> > > Please vote on whether to release Apache ManifoldCF 2.15, RC0.  The
> > > release artifact can be found at:
> > >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.15
> > > .  There is also a release tag at:
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.15-RC0 .
> > >
> > > This release of ManifoldCF ties up some loose ends in the csws
> connector,
> > > and also updates the Solr Connector to the 8.x version of SolrJ.  There
> > are
> > > also some bug fixes included.
> > >
> > > Thanks,
> > > Karl
> > >
> > >
> >
>

Re: [VOTE] Release Apache ManifoldCF Plugin for Solr 8.x, version 2.2 RC0

[Furkan KAMACI]

Hi,

+1 from me.

Kind Regards,
Furkan KAMACI

On Thu, Dec 19, 2019 at 7:25 PM Shinichiro Abe 
wrote:

> +1 from me.
>
> Thanks,
> Shinichiro
>
> 2019年12月19日(木) 17:30 Karl Wright :
>
> > Tests all pass.
> >
> > +1 from me.
> >
> > Karl
> >
> >
> > On Wed, Dec 18, 2019 at 2:39 AM Karl Wright  wrote:
> >
> > > Please vote on whether to release the initial version of the Apache
> > > ManifoldCF Plugin for Solr 8.x, version 2.2, RC0.
> > >
> > > The release artifact can be found here:
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-solr-8.x-plugin-2.2
> > >
> > > There is also a tag at:
> > >
> >
> https://svn.apache.org/repos/asf/manifoldcf/integration/solr-8.x/tags/release-2.2-RC0
> > > .
> > >
> > > Note that the version "2.2" describes, in part, compatibility with
> other
> > > Solr plugins, so is appropriate in this case for an initial version.
> > >
> > > Thanks,
> > > Karl
> > >
> > >
> >
>

Re: Hacktoberfest 2019

[Furkan KAMACI]

Hi Markus,

No, not have a suitable ticket for Hacktoberfest in my mind. However, we
may check whether there are newbie issues or not for such purpose.

Kind Regards,
Furkan KAMACI

On Sun, Sep 29, 2019 at 6:53 PM Markus Schuch  wrote:

> Hi Furkan,
>
> I like that idea.
> Do you have suitable tickets in mind?
>
> As a matter of fact i already booked in for
> https://www.eventbrite.com/e/hacktoberfest-frankfurt-2019-tickets-71269742719.
>
> Cheers,
> Markus
>
> Am 29. September 2019 17:29:57 MESZ schrieb Furkan KAMACI <
> furkankam...@gmail.com>:
>>
>> Hi Fellows,
>>
>> There is an event named as Hacktoberfest
>> https://hacktoberfest.digitalocean.com/
>>
>> It may be great for us to attract new developers. We just need to tag some
>> issues as 'Hacktober'
>> and that's all.
>>
>> What do you think?
>>
>> Kind Regards,
>> Furkan KAMACI
>>
>>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.
>

Re: [VOTE] Release Apache ManifoldCF 2.14, RC2

[Furkan KAMACI]

Hi,

+1 from me.

I checked:
- LICENSE and NOTICE are fine
- NOTICE needs to be updated (check my comment below)
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
- Code compiles and tests successfully run

There is only one minor objection from me which is NOTICE file does not
include up-to-date year for copyright. I've created a PR for it.

Kind Regards,
Furkan KAMACI

On Mon, Sep 30, 2019 at 11:22 AM Karl Wright  wrote:

> All tests pass.  +1 from me.
> Can anyone else look at this, especially Cihad?  I'm not expecting this to
> fix his import but it will possibly fix his linkage error.
>
> Karl
>
>
> On Wed, Sep 25, 2019 at 9:28 PM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> >
> > There is a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC2 .
> > There is a release artifact at
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> .
> >
> > Note that this release of ManifoldCF has a new connector -- the Content
> > Services Web Services connector.  In order to integrate this connector,
> > changes to the dependencies for web services had to be made, so I urge
> > those using the Alfresco and CMIS connectors to verify this release if at
> > all possible.  Integration tests pass but there's nothing like an on-site
> > test.
> >
> > RC2 also contains a fix for CONNECTORS-1623.
> >
> > RC2 also removes duplicate jars appearing connector-lib that are also in
> > the root directory.  This could potentially cause runtime link errors.
> >
> > Thanks,
> > Karl
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.14, RC1

[Furkan KAMACI]

Hi Julien,

Seems that svn version signatures doesn't match and there maybe a sync
problem.

For further investigation and fix could you file a Jira at Infra?

Kind Regards,
Furkan KAMACI



On Wed, Sep 25, 2019 at 7:41 PM Julien Massiera <
julien.massi...@francelabs.com> wrote:

> The last update was on the 26th august. Who do we need to contact to
> solve this problem ? I need the git repo to test this version with our
> test environment.
>
> For now, the compile and Unit tests are ok on my side.
>
> Julien
>
> On 25/09/2019 16:57, Karl Wright wrote:
> > I have no idea.
> > Karl
> >
> >
> > On Wed, Sep 25, 2019 at 10:55 AM Julien Massiera <
> > julien.massi...@francelabs.com> wrote:
> >
> >> Seems like the github mirror is no more synchronized, am I wrong ?
> >>
> >> On 25/09/2019 15:32, Karl Wright wrote:
> >>> See:  https://issues.apache.org/jira/browse/CONNECTORS-1624
> >>>
> >>> Karl
> >>>
> >>>
> >>> On Wed, Sep 25, 2019 at 9:26 AM Piergiorgio Lucidi <
> >> piergior...@apache.org>
> >>> wrote:
> >>>
> >>>> Ran all the tests.
> >>>>
> >>>> +1 from me.
> >>>>
> >>>> Cheers,
> >>>> PJ
> >>>>
> >>>> Il giorno mar 24 set 2019 alle ore 19:30 Karl Wright <
> >> daddy...@gmail.com>
> >>>> ha scritto:
> >>>>
> >>>>> Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> >>>>>
> >>>>> There is a release tag at
> >>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC1 .
> >>>>> There is a release artifact at
> >>>>>
> >>
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> >>>> .
> >>>>> Note that this release of ManifoldCF has a new connector -- the
> Content
> >>>>> Services Web Services connector.  In order to integrate this
> connector,
> >>>>> changes to the dependencies for web services had to be made, so I
> urge
> >>>>> those using the Alfresco and CMIS connectors to verify this release
> if
> >> at
> >>>>> all possible.  Integration tests pass but there's nothing like an
> >> on-site
> >>>>> test.
> >>>>>
> >>>>> RC1 also contains a fix for CONNECTORS-1623.
> >>>>>
> >>>>> Thanks,
> >>>>> Karl
> >>>>>
> >>>> --
> >>>> Piergiorgio
> >>>>
> >> --
> >> Julien MASSIERA
> >> Directeur développement produit
> >> France Labs – Les experts du Search
> >> Datafari – Vainqueur du trophée Big Data 2018 au Digital Innovation
> Makers
> >> Summit
> >> www.francelabs.com
> >>
> >>
> --
> Julien MASSIERA
> Directeur développement produit
> France Labs – Les experts du Search
> Datafari – Vainqueur du trophée Big Data 2018 au Digital Innovation Makers
> Summit
> www.francelabs.com
>
>

Re: [VOTE] Release Apache ManifoldCF 2.14, RC1

[Furkan KAMACI]

Hi,

+1 from me.

I checked:
- LICENSE and NOTICE are fine
- NOTICE needs to be updated (check my comment below)
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
- Code compiles and tests successfully run

There is only one minor objection from me which is NOTICE file does not
include up-to-date year for copyright. I've created a PR for it.

Kind Regards,
Furkan KAMACI

On Wed, Sep 25, 2019 at 5:57 PM Karl Wright  wrote:

> I have no idea.
> Karl
>
>
> On Wed, Sep 25, 2019 at 10:55 AM Julien Massiera <
> julien.massi...@francelabs.com> wrote:
>
> > Seems like the github mirror is no more synchronized, am I wrong ?
> >
> > On 25/09/2019 15:32, Karl Wright wrote:
> > > See:  https://issues.apache.org/jira/browse/CONNECTORS-1624
> > >
> > > Karl
> > >
> > >
> > > On Wed, Sep 25, 2019 at 9:26 AM Piergiorgio Lucidi <
> > piergior...@apache.org>
> > > wrote:
> > >
> > >> Ran all the tests.
> > >>
> > >> +1 from me.
> > >>
> > >> Cheers,
> > >> PJ
> > >>
> > >> Il giorno mar 24 set 2019 alle ore 19:30 Karl Wright <
> > daddy...@gmail.com>
> > >> ha scritto:
> > >>
> > >>> Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> > >>>
> > >>> There is a release tag at
> > >>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC1 .
> > >>> There is a release artifact at
> > >>>
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> > >> .
> > >>> Note that this release of ManifoldCF has a new connector -- the
> Content
> > >>> Services Web Services connector.  In order to integrate this
> connector,
> > >>> changes to the dependencies for web services had to be made, so I
> urge
> > >>> those using the Alfresco and CMIS connectors to verify this release
> if
> > at
> > >>> all possible.  Integration tests pass but there's nothing like an
> > on-site
> > >>> test.
> > >>>
> > >>> RC1 also contains a fix for CONNECTORS-1623.
> > >>>
> > >>> Thanks,
> > >>> Karl
> > >>>
> > >>
> > >> --
> > >> Piergiorgio
> > >>
> > --
> > Julien MASSIERA
> > Directeur développement produit
> > France Labs – Les experts du Search
> > Datafari – Vainqueur du trophée Big Data 2018 au Digital Innovation
> Makers
> > Summit
> > www.francelabs.com
> >
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.14, RC1

[Furkan KAMACI]

Hi Cihad,

That package is removed at Java 11. It is possible that you compiled the
project via Java 11 which is not supported at ManifoldCF yet.

Kind Regards,
Furkan KAMACI

25 Eyl 2019 Çar, saat 15:00 tarihinde Cihad Guzel  şunu
yazdı:

> Hi Karl,
>
> I have following errors:
>
> [INFO] -< org.apache.manifoldcf:mcf-connector-common
> >-
> [INFO] Building ManifoldCF - Connector-Common 2.14
> [5/63]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> mcf-connector-common ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> mcf-connector-common ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
> mcf-connector-common ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> mcf-connector-common ---
> [INFO] Compiling 59 source files to
>
> /Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
>
> /Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[60,21]
> error: package javax.xml.soap does not exist
> [ERROR]
>
> /Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[61,21]
> error: package javax.xml.soap does not exist
> [ERROR]
>
> /Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[62,21]
> error: package javax.xml.soap does not exist
> [INFO] 3 errors
>
> Regards,
> Cihad Guzel
>
>
> Karl Wright , 25 Eyl 2019 Çar, 02:01 tarihinde şunu
> yazdı:
>
> > Ran all tests.
> >
> > +1 from me.
> >
> > Karl
> >
> >
> > On Tue, Sep 24, 2019 at 1:29 PM Karl Wright  wrote:
> >
> > > Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> > >
> > > There is a release tag at
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC1 .
> > > There is a release artifact at
> > >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> > .
> > >
> > > Note that this release of ManifoldCF has a new connector -- the Content
> > > Services Web Services connector.  In order to integrate this connector,
> > > changes to the dependencies for web services had to be made, so I urge
> > > those using the Alfresco and CMIS connectors to verify this release if
> at
> > > all possible.  Integration tests pass but there's nothing like an
> on-site
> > > test.
> > >
> > > RC1 also contains a fix for CONNECTORS-1623.
> > >
> > > Thanks,
> > > Karl
> > >
> >
>

Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.14, RC0

[Furkan KAMACI]

Hi Karl,

Thanks for the information! On the other hand, hope your family member get
well soon.

Kind Regards,
Furkan KAMACI

On Tue, Sep 24, 2019 at 8:47 PM Karl Wright  wrote:

> Hi Furkan,
>
> We do not do this as part of the release process.  The tags are versioned
> but the artifacts are named the same.  Only one of them ever is released so
> this is OK; the older artifacts are put in a different folder labeled
> "RC0", "RC1", etc.
>
> This process was originally designed by Jukka Zitting and Grant Ingersoll
> when MCF was graduating from the incubator and we have not changed it.
>
> Karl
>
>
> On Tue, Sep 24, 2019 at 1:36 PM Furkan KAMACI 
> wrote:
>
> > Hi Karl,
> >
> > I didn't want to hijack latest vote thread. Do we need to add a suffix as
> > like RC-1 to dist file as like here:
> > https://dist.apache.org/repos/dist/dev/zookeeper/ ?
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Tue, Sep 24, 2019 at 7:32 PM Karl Wright  wrote:
> >
> > > CONNECTORS-1623.
> > >
> > > On Tue, Sep 24, 2019 at 9:04 AM Karl Wright 
> wrote:
> > >
> > > > Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> > > >
> > > > There is a release tag at
> > > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC0 .
> > > > There is a release artifact at
> > > >
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> > > .
> > > >
> > > > Note that this release of ManifoldCF has a new connector -- the
> Content
> > > > Services Web Services connector.  In order to integrate this
> connector,
> > > > changes to the dependencies for web services had to be made, so I
> urge
> > > > those using the Alfresco and CMIS connectors to verify this release
> if
> > at
> > > > all possible.  Integration tests pass but there's nothing like an
> > on-site
> > > > test.
> > > >
> > > > Thanks,
> > > > Karl
> > > >
> > > >
> > >
> >
>

Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.14, RC0

[Furkan KAMACI]

Hi Karl,

I didn't want to hijack latest vote thread. Do we need to add a suffix as
like RC-1 to dist file as like here:
https://dist.apache.org/repos/dist/dev/zookeeper/ ?

Kind Regards,
Furkan KAMACI

On Tue, Sep 24, 2019 at 7:32 PM Karl Wright  wrote:

> CONNECTORS-1623.
>
> On Tue, Sep 24, 2019 at 9:04 AM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> >
> > There is a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC0 .
> > There is a release artifact at
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> .
> >
> > Note that this release of ManifoldCF has a new connector -- the Content
> > Services Web Services connector.  In order to integrate this connector,
> > changes to the dependencies for web services had to be made, so I urge
> > those using the Alfresco and CMIS connectors to verify this release if at
> > all possible.  Integration tests pass but there's nothing like an on-site
> > test.
> >
> > Thanks,
> > Karl
> >
> >
>

Re: Minimum JDK version supported

[Furkan KAMACI]

Hi Raman,

Yes, supported version is 1.8:
https://github.com/apache/manifoldcf/blob/trunk/pom.xml

Kind Regards,
Furkan KAMACI

27 Ağu 2019 Sal, saat 20:37 tarihinde Raman Gupta 
şunu yazdı:

> What is the minimum JDK version intended to be supported by ManifoldCF
> as of the current version? Is it 1.8?
>
> Regards,
> Raman
>

Re: Unexpected HTTP result code: -1: null

[Furkan KAMACI]

Hi Priya,

Set Xms and Xmx values as same. Try with a fairly bigger value, i.e. 4096m
or more and share the result. Then we can adjust that value.

What is your main purpose to use ManifoldCF, just web crawl? If so, you can
check Apache Nutch project too.

Kind Regards,
Furkan KAMACI

16 Ağu 2019 Cum, saat 13:55 tarihinde Priya Arora 
şunu yazdı:

> Hi Furkan,
>
> These are the configuration defined  I have -Xms1024m ,-Xmx1024m memory
> allocated *in start-options.env.unix, start-options.env.win* file.
> Also Configuration:-
> 1) For Crawler server - 16 GB RAM and 8-Core Intel(R) Xeon(R) CPU E5-2660
> v3 @ 2.60GHz and -ManifolCF
>
> 2) For Elasticsearch server - 48GB and 1-Core Intel(R) Xeon(R) CPU E5-2660
> v3 @ 2.60GHz and i am using postgres as database.
>
> When this parameter -Xms1024m was set as -Xms512m., even then i was facing
> this error.
>
> Thanks and Regards
> Priya
>
> On Fri, Aug 16, 2019 at 4:21 PM Furkan KAMACI 
> wrote:
>
> > Hi Priya,
> >
> > What is your GC params and does it throw error at a particular Zip file?
> > Check its size and if much, consider limiting allowed file size to
> ingest.
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > 16 Ağu 2019 Cum, saat 13:40 tarihinde Karl Wright 
> > şunu
> > yazdı:
> >
> > > I see nothing indicating any single Tika extraction content type.  It's
> > > basically just unhappy with heap fragmentation and is GC'ing too
> > > frequently.  I would suggest just increasing the amount of memory you
> > give
> > > the process for an experiment.  This might allow it to succeed.
> > >
> > > MCF uses the principle of "bounded memory", which means that every
> > > connector cannot put whole documents into memory, but must be limited.
> > But
> > > there is no stipulation as to any specific limit that each connector
> must
> > > work within.  Some connectors, therefore, use a lot more memory than
> > > others, and Tika is one of the ones that can use a lot.  But it is
> still
> > > bounded unless there's a bug, so just try increasing for a start.
> > >
> > > Karl
> > >
> > >
> > > On Fri, Aug 16, 2019 at 6:25 AM Priya Arora 
> wrote:
> > >
> > > > Please Find below error stack trace:-
> > > >
> > > > ERROR: agents process ran out of memory - shutting down
> > > > java.lang.OutOfMemoryError: GC overhead limit exceeded
> > > > at java.util.HashMap.newNode(HashMap.java:1750)
> > > > at java.util.HashMap.putVal(HashMap.java:631)
> > > > at java.util.HashMap.put(HashMap.java:612)
> > > > at
> > > > org.apache.manifoldcf.connectorcommon.fuzzyml.HTMLParseState.noteTag(
> > > >
> > > >  HTMLParseState.java:51)
> > > > at
> > > > org.apache.manifoldcf.connectorcommon.fuzzyml.TagParseState.dealWithC
> > > >
> > > >  haracter(TagParseState.java:638)
> > > > at
> > > > org.apache.manifoldcf.connectorcommon.fuzzyml.SingleCharacterReceiver
> > > >
> > > >  .dealWithCharacters(SingleCharacterReceiver.java:51)
> > > > at
> > > >
> org.apache.manifoldcf.connectorcommon.fuzzyml.DecodingByteReceiver.de
> > > >
> > > >  alWithBytes(DecodingByteReceiver.java:48)
> > > > at
> > > > org.apache.manifoldcf.connectorcommon.fuzzyml.Parser.parseWithoutChar
> > > >
> > > >  setDetection(Parser.java:99)
> > > > at
> > > > org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
> > > >
> > > >  or.handleHTML(WebcrawlerConnector.java:4918)
> > > > at
> > > > org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
> > > >
> > > >  or.extractLinks(WebcrawlerConnector.java:3852)
> > > > at
> > > > org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
> > > >
> > > >  or.processDocuments(WebcrawlerConnector.java:747)
> > > > at
> > > > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja
> > > >
> > > >  va:399)
> > > > agents process ran out of memory - shutting down
> > > > java.lang.OutOfMemoryError: GC overhead limit exceeded
> > > > agents process ran out of memory - shutting down
> > > > java.lang.Ou

Re: Unexpected HTTP result code: -1: null

[Furkan KAMACI]

Hi Priya,

What is your GC params and does it throw error at a particular Zip file?
Check its size and if much, consider limiting allowed file size to ingest.

Kind Regards,
Furkan KAMACI

16 Ağu 2019 Cum, saat 13:40 tarihinde Karl Wright  şunu
yazdı:

> I see nothing indicating any single Tika extraction content type.  It's
> basically just unhappy with heap fragmentation and is GC'ing too
> frequently.  I would suggest just increasing the amount of memory you give
> the process for an experiment.  This might allow it to succeed.
>
> MCF uses the principle of "bounded memory", which means that every
> connector cannot put whole documents into memory, but must be limited.  But
> there is no stipulation as to any specific limit that each connector must
> work within.  Some connectors, therefore, use a lot more memory than
> others, and Tika is one of the ones that can use a lot.  But it is still
> bounded unless there's a bug, so just try increasing for a start.
>
> Karl
>
>
> On Fri, Aug 16, 2019 at 6:25 AM Priya Arora  wrote:
>
> > Please Find below error stack trace:-
> >
> > ERROR: agents process ran out of memory - shutting down
> > java.lang.OutOfMemoryError: GC overhead limit exceeded
> > at java.util.HashMap.newNode(HashMap.java:1750)
> > at java.util.HashMap.putVal(HashMap.java:631)
> > at java.util.HashMap.put(HashMap.java:612)
> > at
> > org.apache.manifoldcf.connectorcommon.fuzzyml.HTMLParseState.noteTag(
> >
> >  HTMLParseState.java:51)
> > at
> > org.apache.manifoldcf.connectorcommon.fuzzyml.TagParseState.dealWithC
> >
> >  haracter(TagParseState.java:638)
> > at
> > org.apache.manifoldcf.connectorcommon.fuzzyml.SingleCharacterReceiver
> >
> >  .dealWithCharacters(SingleCharacterReceiver.java:51)
> > at
> > org.apache.manifoldcf.connectorcommon.fuzzyml.DecodingByteReceiver.de
> >
> >  alWithBytes(DecodingByteReceiver.java:48)
> > at
> > org.apache.manifoldcf.connectorcommon.fuzzyml.Parser.parseWithoutChar
> >
> >  setDetection(Parser.java:99)
> > at
> > org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
> >
> >  or.handleHTML(WebcrawlerConnector.java:4918)
> > at
> > org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
> >
> >  or.extractLinks(WebcrawlerConnector.java:3852)
> > at
> > org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
> >
> >  or.processDocuments(WebcrawlerConnector.java:747)
> > at
> > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja
> >
> >  va:399)
> > agents process ran out of memory - shutting down
> > java.lang.OutOfMemoryError: GC overhead limit exceeded
> > agents process ran out of memory - shutting down
> > java.lang.OutOfMemoryError: GC overhead limit exceeded
> > at java.nio.ByteBuffer.wrap(ByteBuffer.java:373)
> > at java.nio.ByteBuffer.wrap(ByteBuffer.java:396)
> > at
> > org.apache.commons.compress.archivers.zip.ZipFile.resolveLocalFileHea
> >
> >  derData(ZipFile.java:1059)
> > at
> > org.apache.commons.compress.archivers.zip.ZipFile.(ZipFile.java
> >
> >  :296)
> > at
> > org.apache.commons.compress.archivers.zip.ZipFile.(ZipFile.java
> >
> >  :218)
> > at
> > org.apache.commons.compress.archivers.zip.ZipFile.(ZipFile.java
> >
> >  :201)
> > at
> > org.apache.commons.compress.archivers.zip.ZipFile.(ZipFile.java
> >
> >  :162)
> > at
> > org.apache.tika.parser.pkg.ZipContainerDetector.detectOPCBased(ZipCon
> >
> >  tainerDetector.java:241)
> > at
> > org.apache.tika.parser.pkg.ZipContainerDetector.detectZipFormat(ZipCo
> >
> >  ntainerDetector.java:173)
> > at
> > org.apache.tika.parser.pkg.ZipContainerDetector.detect(ZipContainerDe
> >
> >  tector.java:110)
> > at
> > org.apache.tika.detect.CompositeDetector.detect(CompositeDetector.jav
> >
> >  a:84)
> > at
> > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:1
> >
> >  16)
> > at
> > org.apache.tika.parser.DelegatingParser.parse(DelegatingParser.java:7
> >
> >  2)
> > at
> > org.apache.tika.extractor.ParsingEmbeddedDocumentExtractor.parseEmbed
> >
> >  ded(ParsingEmbeddedDocumentExtract

Re: ManifoldCF Resource Offering

[Furkan KAMACI]

Hi Michael,

Thanks for your interest!

Community is important for FOSS projects. It can both help to develop such
improvements and use it as may need them.

So, in my opinion you can share which parts do you want to improve/add and
share it with us for both some can help you and need them.

Kind Regards,
Furkan KAMACI

16 Ağu 2019 Cum, saat 07:13 tarihinde Karl Wright  şunu
yazdı:

> Excellent!
> Thanks for contacting us.  I hope we can help.
>
> Karl
>
> On Thu, Aug 15, 2019 at 9:17 PM Michael Cizmar 
> wrote:
>
> > Hey Folks,
> >
> > I exchanged emails with Karl earlier this week, but I wanted to reach out
> > to you to offer up some additional assistance for the ManifoldCF project.
> > My firm has previously written about a dozen commercial connectors
> > primarily targeted to the Google Search Appliance.  We are starting to
> use
> > the ManifoldCF platform as a web crawler for Elasticsearch but have plans
> > to expand it work with some of the other platforms that we work with.
> >
> >
> >
> > I am planning on contributing to the code base  and potentially offering
> > commercial support to our clients.  Would like to get your thoughts on
> that
> > and where you think our assistance could be best utilized.
> >
> >
> > Thanks!
> >
> >
> > Michael
> >
>

Re: Reminder: August 31st is the next scheduled ManifoldCF release

[Furkan KAMACI]

Hi Karl,

I am OK with a new release. However, we can rediscuss every two weeks as
you suggested.

Kind Regards,
Furkan KAMACI

14 Ağu 2019 Çar, saat 01:19 tarihinde Karl Wright  şunu
yazdı:

> If tickets are proceeding we can hold off, for a while.  I think we should
> rediscuss every two weeks or so.
>
> Karl
>
>
> On Tue, Aug 13, 2019 at 5:49 PM Markus Schuch 
> wrote:
>
> > Hi,
> >
> > i looked through the issues scheduled for 2.14
> >
> > looks like
> > https://issues.apache.org/jira/browse/CONNECTORS-1591
> > could be adressed by a tika upgrade. May be this is still achievable?
> >
> > We made some progress with testing the new CSWS connector at my company.
> > I think there will be some feedback in the next days. But 31th august
> > seems to close to get this finished.
> >
> > The other tickets marked for 2.14 seem to wait on external resources.
> >
> > In addition i just resumed
> > https://issues.apache.org/jira/browse/CONNECTORS-1105. May be we get
> > this done and can add this to the release.
> >
> > Markus
> >
> > Am 12.08.2019 um 14:57 schrieb Karl Wright:
> > > I had hoped that we could finish the OpenText Content Service/Web
> Service
> > > connector by this release cycle but I do not think it will be finished.
> > So
> > > I suggest we go ahead with release plans.  It's a pretty light release
> > I'm
> > > afraid.
> > >
> > > Thoughts?
> > > Karl
> > >
> >
>

[jira] [Commented] (CONNECTORS-1611) Update MySQL Version

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1611:
---

[~kwri...@metacarta.com] could you check this PR?

> Update MySQL Version
> 
>
> Key: CONNECTORS-1611
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1611
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: JDBC connector
>Affects Versions: ManifoldCF 2.13
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
>Priority: Critical
>
> New MySQL versions come with *caching_sha2_password*. mysql-connector before 
> version 5.1.46 does not have such compatibility and users get this error:
> {code:java}
> java.sql.SQLException: Unable to load authentication plugin 
> 'caching_sha2_password'.
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (CONNECTORS-1611) Update MySQL Version

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1611:
---

Created a PR: https://github.com/apache/manifoldcf/pull/99

> Update MySQL Version
> 
>
> Key: CONNECTORS-1611
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1611
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: JDBC connector
>Affects Versions: ManifoldCF 2.13
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
>Priority: Critical
>
> New MySQL versions come with *caching_sha2_password*. mysql-connector before 
> version 5.1.46 does not have such compatibility and users get this error:
> {code:java}
> java.sql.SQLException: Unable to load authentication plugin 
> 'caching_sha2_password'.
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CONNECTORS-1611) Update MySQL Version

[Furkan KAMACI (JIRA)]

Furkan KAMACI created CONNECTORS-1611:
-

 Summary: Update MySQL Version
 Key: CONNECTORS-1611
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1611
 Project: ManifoldCF
  Issue Type: Improvement
  Components: JDBC connector
Affects Versions: ManifoldCF 2.13
Reporter: Furkan KAMACI
Assignee: Furkan KAMACI


New MySQL versions come with *caching_sha2_password*. mysql-connector before 
version 5.1.46 does not have such compatibility and users get this error:

{code:java}
java.sql.SQLException: Unable to load authentication plugin 
'caching_sha2_password'.
{code}





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: ManifoldCF Website Links

[Furkan KAMACI]

Hep about adding a path as latest i.e.:

https://manifoldcf.apache.org/release/latest/en_US/performance-tuning.html


22 Şub 2019 Cum, saat 11:34 tarihinde Karl Wright  şunu
yazdı:

> Hi Furkan,
>
> I am not sure why Google maintains these dead links but we simply cannot
> publish doc for every release going back to 2012.  Generally we cycle
> releases and include the last two for each major release.  We include the
> 1.10 docs as well as the 2.12 and 2.11 docs right now.  It is prohibitively
> expensive to include more than that; doing so would make it incrementally
> harder to update the site, and it's already not easy.
>
> Thanks,
> Karl
>
>
> On Fri, Feb 22, 2019 at 2:34 AM Furkan KAMACI 
> wrote:
>
> > Hi All,
> >
> > When we search something on ManifoldCF on Google we get results something
> > like that:
> >
> >
> >
> https://manifoldcf.apache.org/release/release-2.9.1/en_US/performance-tuning.html
> >
> > However, such links are broken. Can we fix it someway i.e. creating a
> path
> > for latest release?
> >
> > Kind Regards,
> > Furkan KAMACI
> >
>

ManifoldCF Website Links

[Furkan KAMACI]

Hi All,

When we search something on ManifoldCF on Google we get results something
like that:

https://manifoldcf.apache.org/release/release-2.9.1/en_US/performance-tuning.html

However, such links are broken. Can we fix it someway i.e. creating a path
for latest release?

Kind Regards,
Furkan KAMACI

Re: About publishing in mvn central repository

[Furkan KAMACI]

Hi,

Here is an explanation for publishing Maven artifacts for Ant + Ivy at
Apache:

http://www.apache.org/dev/publishing-maven-artifacts.html#ant

Kind Regards,
Furkan KAMACI

On Wed, Jan 30, 2019 at 3:23 PM Karl Wright  wrote:

> There's a ticket outstanding for this but nobody could figure out how to do
> it, since the jars are built with Ant not Maven.
>
> If you want to work out how, please feel free to go ahead.
>
> Karl
>
> On Wed, Jan 30, 2019 at 7:08 AM Cihad Guzel  wrote:
>
> > Hi,
> >
> > There aren't Manifoldcf jar packages in the mvn central repository. Maybe
> > they can be published in the repository? So we can add mcf-core or other
> > mfc jar packages to our projects as dependency.
> >
> > What do you think about that?
> >
> > [1]
> > https://maven.apache.org/repository/guide-central-repository-upload.html
> >
> >
> > Regards,
> > Cihad Güzel
> >
>

Mambo CMS

[Furkan KAMACI]

Hi All,

Mambo (http://mambo-foundation.org) is an open source CMS system which is
being used by many companies.

Do we have a Mambo integration via ManifoldCF or does anybody knows Mambo
supports our CMIS connector?

If not, we can suggest it as a GSoC project for 2019.

Kind Regards,
Furkan KAMACI

[jira] [Commented] (CONNECTORS-1561) Upgrade to Tika 1.20 when available

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1561:
---

Tika has released 1.20. Changes can be found from here: 
http://tika.apache.org/1.20/

> Upgrade to Tika 1.20 when available
> ---
>
> Key: CONNECTORS-1561
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1561
> Project: ManifoldCF
>  Issue Type: Improvement
>Reporter: Tim Allison
>Priority: Major
>
> On TIKA-2776, a ManifoldCF user alerted us to a bad bug in Tika 1.19 and 
> 1.19.1 that causes tika-server to return 503 forever after it hits an OOM.  
> This is bad.  We'll be rolling a fix out in a week or two in Tika 1.20.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache ManifoldCF 2.12, RC0

[Furkan KAMACI]

+1 from me too!

On Thu, Dec 20, 2018 at 3:39 PM Karl Wright  wrote:

> Folks, I need one more vote.
>
> Steph, would you want to look at the artifact and make sure it works for
> Elasticsearch?  A lot of ES-specific enhancements were added...
>
> Karl
>
>
> On Mon, Dec 17, 2018 at 9:20 AM Rafa Haro  wrote:
>
> > Downloaded Source Code and built the project
> >
> > +1 from me
> >
> > On Mon, Dec 17, 2018 at 2:25 PM Karl Wright  wrote:
> >
> > > Ran all tests.
> > >
> > > +1 from me.
> > >
> > > Karl
> > >
> > >
> > > On Sun, Dec 16, 2018 at 3:15 PM Karl Wright 
> wrote:
> > >
> > > > Please vote on whether to release Apache ManifoldCF 2.12, RC0.
> > > >
> > > > The release artifact can be found at:
> > > >
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.12
> > > > .  There is also a release tag at:
> > > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.12-RC0 .
> > > >
> > > > This release is notable because it includes significant improvements
> to
> > > > the ElasticSearch connector, along with a fix for a long-standing
> > > hopcount
> > > > bug (more than five years old!)
> > > >
> > > > Thanks in advance,
> > > > Karl
> > > >
> > > >
> > >
> >
>

[jira] [Commented] (CONNECTORS-1563) SolrException: org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 bytes

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1563:
---

Please check here: issues.apache.org/jira/browse/TIKA-2637

> SolrException: org.apache.tika.exception.ZeroByteFileException: InputStream 
> must have > 0 bytes
> ---
>
> Key: CONNECTORS-1563
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1563
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Solr 7.x component
>Reporter: Sneha
>Priority: Major
>
> I am encountering this problem:
> I have checked "Use the Extract Update Handler:" param then I am getting an 
> error on Solr i.e. null:org.apache.solr.common.SolrException: 
> org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 
> bytes
> If I ignore tika exception, my documents get indexed but dont have content 
> field on Solr.
> I am using Solr 7.3.1 and manifoldCF 2.8.1
> I am using solr cell and hence not configured external tika extractor in 
> manifoldCF pipeline
> Please help me with this problem
> Thanks in advance



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1553) Upgrade to SolrJ 6.6.5

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1553:
--
Summary: Upgrade to SolrJ 6.6.5  (was: Upgrade to SolrJ 6.5.0)

> Upgrade to SolrJ 6.6.5
> --
>
> Key: CONNECTORS-1553
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1553
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.11
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
>Priority: Major
> Fix For: ManifoldCF 2.12
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1553) Upgrade to SolrJ 6.5.0

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1553:
---

I've created a PR at Github. Path file can be seen from here: 
https://patch-diff.githubusercontent.com/raw/apache/manifoldcf-integration-solr-6.x/pull/1.patch

> Upgrade to SolrJ 6.5.0
> --
>
> Key: CONNECTORS-1553
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1553
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.11
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
>Priority: Major
> Fix For: ManifoldCF 2.12
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CONNECTORS-1553) Upgrade to SolrJ 6.5.0

[Furkan KAMACI (JIRA)]

Furkan KAMACI created CONNECTORS-1553:
-

 Summary: Upgrade to SolrJ 6.5.0
 Key: CONNECTORS-1553
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1553
 Project: ManifoldCF
  Issue Type: Task
  Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 2.11
Reporter: Furkan KAMACI
Assignee: Furkan KAMACI
 Fix For: ManifoldCF 2.12






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Asking for a ManifoldCF blog

[Furkan KAMACI]

Hi Piergiorgio!

I would like to be at the editors team too!

Kind Regards,
Furkan KAMACI

On Fri, May 4, 2018 at 12:40 PM Piergiorgio Lucidi <piergior...@apache.org>
wrote:

> Hi,
>
> I have just asked to the INFRA Team for a dedicated blog available in the
> Apache Roller Weblog [1].
>
> I think it could be very useful to share detailed informations about each
> release / development related to the project.
>
> Our blog will be available from the official Apache blogs platform [2] with
> the dedicated manifoldcf context path.
>
> I asked to enable me and Karl for writing post but please let me know if
> anybody else want to join the editors team.
>
> Hope this helps :)
>
> --
> Piergiorgio
>
> [1] - https://issues.apache.org/jira/browse/INFRA-16481
> [2] - https://blogs.apache.org/
>

Re: [ANNOUNCE] - Welcome Irindu Nugawela as GSoC student at ASF

[Furkan KAMACI]

Welcome Irindu!

On Tue, Apr 24, 2018 at 1:34 PM, Irindu Nugawela 
wrote:

> Hi all,
> Thank you very much for your support. I am thrilled to be a part of Apache
> Software Foundation contributing to ManifoldCF,  I am hoping to do my best
> with this valuable opportunity.  Looking forward to working with you.
>
> On 24 April 2018 at 15:01, Rafa Haro  wrote:
>
> > Welcome Irindu. Hope you have fun working with ManifoldCF!
> >
> > Looking forward for your contributions!
> >
> > On Tue, Apr 24, 2018 at 9:11 AM Piergiorgio Lucidi <
> piergior...@apache.org>
> > wrote:
> >
> >> Hi all,
> >>
> >> we have joined the Google Summer Of Code 2018 and we have a new
> >> contributor
> >> in the community :)
> >>
> >> Please join me in welcoming Irindu Nugawela as GSoC student on
> ManifoldCF,
> >> he we will help us on implementing the new MongoDB Output Connector [1].
> >>
> >> The status of his proposal is officially accepted from both ASF and
> Google
> >> [2], so we can officially start and I'll try to support him during this
> >> journey.
> >>
> >> The plan for this proposal is the following:
> >>
> >>1. April: Setup development environment
> >>2. May: Basic implementation for configuring the connector with unit
> >>tests
> >>3. June: Crawling methods and unit tests
> >>4. July: Integration Tests and bugfixing
> >>5. August: Write documentation, code cleanup and bugfixing
> >>
> >> I have to confess that Irindu has anticipated some steps, I think that
> >> actually we are in step 3. Great job Irindu ;)
> >>
> >> [1] - https://issues.apache.org/jira/browse/CONNECTORS-1490
> >> [2] - https://summerofcode.withgoogle.com/projects/#4692864580190208
> >>
> >> --
> >> Piergiorgio Lucidi
> >> https://www.open4dev.com
> >>
> >
>
>
> --
> Thanks and Regards,
> Irindu Nugawela,
> Computer Engineering  Undergraduate,
> Faculty of Engineering University of Peradeniya
>

Re: [VOTE] Release ManifoldCF 2.10, RC0

[Furkan KAMACI]

+1 from me too.

On Mon, Apr 16, 2018 at 4:17 PM, Piergiorgio Lucidi 
wrote:

> +1 from me.
>
> I don't see any issue, I have just ran tests and if I try to run the
> distribution built from the source code, I see all the connectors correctly
> registered.
>
> PJ
>
> 2018-04-16 13:01 GMT+02:00 Karl Wright :
>
> > Everything looks good here, but I did notice that our copyright notice
> > needs to be updated to 2018.  I'll commit that in case we really do need
> to
> > spin another RC.
> >
> > Karl
> >
> >
> > On Mon, Apr 16, 2018 at 6:52 AM, Rafa Haro  wrote:
> >
> > > my own build yes
> > >
> > > On Mon, Apr 16, 2018 at 12:23 PM Karl Wright 
> wrote:
> > >
> > > > hmm, I can't seem to reproduce this.
> > > >
> > > > This was your own build, not the binary?
> > > >
> > > > Karl
> > > >
> > > > On Mon, Apr 16, 2018 at 4:13 AM, Rafa Haro  wrote:
> > > >
> > > > > Not sure if it is an issue but:
> > > > >
> > > > > I have downloaded source code, built with maven and ant without
> > > problems.
> > > > > Then I started the system at dist/example/start.sh. After starting
> > up I
> > > > > couldn't configure any connector getting always the message "No
> > > > connectors
> > > > > registered". Nothing in the logs
> > > > >
> > > > > On Sun, Apr 15, 2018 at 7:30 PM Karl Wright 
> > > wrote:
> > > > >
> > > > > > Please vote on whether to release ManifoldCF 2.10, RC0.
> > > > > >
> > > > > > The release artifacts can be found at
> > > > > >
> > > > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-man
> > ifoldcf-2.10
> > > > > .
> > > > > > There is also a release tag at
> > > > > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.
> 10-RC0
> > .
> > > > > >
> > > > > > This release contains a number of fixes and new features.  These
> > are
> > > > > > summarized in
> > > > > >
> > > > > > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-
> > > > > manifoldcf-2.10/CHANGES.txt
> > > > > > .
> > > > > >
> > > > > > Thanks,
> > > > > > Karl
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Piergiorgio Lucidi
> https://www.open4dev.com
>

Re: [VOTE] Release Apache ManifoldCF plugin for Solr 7.x, version 2.2.1, RC0

[Furkan KAMACI]

Hi,

+1 from me.

I've built it and ran tests.

Kind Regards,
Furkan KAMACI

On Thu, Mar 1, 2018 at 5:53 PM, Karl Wright <daddy...@gmail.com> wrote:

> We still need one more +1 for this release.
>
> Karl
>
> On Tue, Feb 27, 2018 at 10:33 AM, Karl Wright <daddy...@gmail.com> wrote:
>
> > It built and the tests ran.  +1 from me.
> > Karl
> >
> >
> > On Sun, Feb 25, 2018 at 9:57 PM, Shinichiro Abe <
> > shinichiro.ab...@gmail.com> wrote:
> >
> >> +1 from me.
> >>
> >> - ran tests.
> >>
> >> Thank you for your support.
> >>
> >> Shinichiro Abe
> >>
> >> 2018-02-26 8:00 GMT+09:00 Karl Wright <daddy...@gmail.com>:
> >>
> >> > Please vote on whether to release the Apache ManifoldCF plugin for
> Solr
> >> > 7.x, version 2.2.1, RC0.
> >> >
> >> > This point release was necessary because Solr added a new dependency
> in
> >> > 7.2.1 and the tests would not run without adding this.
> >> >
> >> > The artifact can be found at:
> >> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-
> >> > manifoldcf-solr-7.x-plugin-2.2.1
> >> > .  There's also a release tag at:
> >> > https://svn.apache.org/repos/asf/manifoldcf/integration/
> >> > solr-7.x/tags/release-2.2.1-RC0
> >> > .
> >> >
> >> > Thanks in advance for your vote!
> >> >
> >> > Karl
> >> >
> >>
> >
> >
>

Re: Apache EU Roadshow CFP Closing Soon (23 February)

[Furkan KAMACI]

Hi Piergiorgio,

I would like to be there to arrange a ManifoldCF meeting! I want to join
you for that proposal.

Kind Regards,
Furkan KAMACI

On Thu, Feb 15, 2018 at 10:32 AM, Piergiorgio Lucidi <piergior...@apache.org
> wrote:

> Hi,
>
> we have a great opportunity to arrange a ManifoldCF meeting during the
> next Apache EU Roadshow that will be co-located with FOSS Backstage in
> Berlin.
>
> Do you want to join the event?
> I can send a proposal for reserving our space at the venue.
>
> Hope to receive a lot of interested people.
> Please let me know if you want to join a potential ManifoldCF hackathon or
> a workshop and then we can arrange it.
>
> Cheers,
> PJ
>
>
> -- Forwarded message --
> From: Sharan F <sha...@apache.org>
> Date: 2018-02-14 16:18 GMT+01:00
> Subject: Apache EU Roadshow CFP Closing Soon (23 February)
> To:
>
>
> Hello Everyone
>
> This is an initial reminder to let you all know that we are holding an
> Apache EU Roadshow co-located with FOSS Backstage in Berlin on 13th and 14
> th June 2018. https://s.apache.org/tCHx
>
> The Call for Proposals (CFP) for the Apache EU Roadshow is currently open
> and will close at the end of next week, so if you have been delaying making
> a submission because the closing date seemed a long way off, then it's time
> to start getting your proposals submitted.
>
> So what are we looking for?
> We will have 2 Apache Devrooms available during the 2 day Roadshow so are
> looking for projects including incubating ones, to submit presentations,
> panel discussions, BoFs, or workshop proposals. The main focus of the
> Roadshow will be IoT, Cloud, Httpd and Tomcat so if your project is
> involved in or around any of these technologies at Apache then we are very
> interested in hearing from you.
>
> Community and collaboration is important at Apache so if your project is
> interested in organising a project sprint, meetup or hackathon during the
> Roadshow, then please submit it in the CFP as we do have some space
> available to allocate for these.
>
> If you are wanting to submit a talk on open source community related
> topics such as the Apache Way, governance or legal aspects then please
> submit these to the CFP for FOSS Backstage.
>
> Tickets for the Apache EU Roadshow are included as part of the
> registration for FOSS Backstage, so to attend the Roadshow you will need to
> register for FOSS Backstage. Early Bird tickets are still available until
> the 21st February 2018.
>
> Please see below for important URLs to remember:
>
> -  To submit a CFP for the Apache EU Roadshow :
> http://apachecon.com/euroadshow18/
>
> -  To submit a CFP for FOSS Backstage : https://foss-backstage.de/call
> -papers
>
> -  To register to attend the Apache EU Roadshow and/or FOSS Backstage :
> https://foss-backstage.de/tickets
>
> For further updates and information about the Apache EU Roadshow please
> check http://apachecon.com/euroadshow18/
>
> Thanks
> Sharan Foga, VP Apache Community Development
>
>
>
> --
> Piergiorgio Lucidi
> https://www.open4dev.com
>

Re: [VOTE] Release ManifoldCF 2.9.1, RC0

[Furkan KAMACI]

Hi,

+1 from me!

Kind Regards,
Furkan KAMACI


14 Oca 2018 Paz, saat 21:34 tarihinde Karl Wright <daddy...@gmail.com> şunu
yazdı:

> Still need one more vote...
>
> Karl
>
> On Sat, Jan 13, 2018 at 12:46 PM, Markus Schuch <markus_sch...@web.de>
> wrote:
>
> > Looked through the diff, built the rc0-tag and ran all tests
> successfully.
> >
> > Also crawled some MS word docs with the tika transformer and ingested
> > them successfully into solr 7.2 without any errors.
> >
> > +1 from me
> >
> > Am 12.01.2018 um 18:57 schrieb Karl Wright:
> > > The user who logged the bug reports that RC0 fixed his problem, so +1
> > from
> > > me.
> > >
> > > Karl
> > >
> > >
> > > On Fri, Jan 12, 2018 at 11:56 AM, Karl Wright <daddy...@gmail.com>
> > wrote:
> > >
> > >> This point release was made necessary by incompatibilities between our
> > POI
> > >> version and Tika version in 2.9.  (CONNECTORS-1481).  I've also
> included
> > >> the fix for CONNECTORS-1478 in the release.
> > >>
> > >> Please vote on whether to release this artifact.  The artifact can be
> > >> found at:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-
> > manifoldcf-2.9.1
> > >>
> > >> There is also a tag at:
> > >>
> > >> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.9.1-RC0
> > >>
> > >> Thanks!
> > >> Karl
> > >>
> > >>
> > >
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.9, RC2

[Furkan KAMACI]

Hi,

+1 from me.

Kind Regards,
Furkan KAMACI

On Wed, Dec 20, 2017 at 4:15 PM, Piergiorgio Lucidi <piergior...@apache.org>
wrote:

> Ran tests, this time using Ant :-P
>
> +1 from me.
>
> 2017-12-20 13:57 GMT+01:00 Karl Wright <daddy...@gmail.com>:
>
> > Ran tests.  +1 from me.
> >
> > Karl
> >
> >
> > On Tue, Dec 19, 2017 at 10:41 PM, Shinichiro Abe <
> > shinichiro.ab...@gmail.com
> > > wrote:
> >
> > > Hi,
> > >
> > > Ran tests, unpacked the bin and ran a job.
> > >
> > > +1 from me.
> > >
> > > Shinichiro Abe
> > >
> > > 2017-12-20 5:44 GMT+09:00 Karl Wright <daddy...@gmail.com>:
> > >
> > > > Please vote on whether to release Apache ManifoldCF 2.9, RC2.
> > > >
> > > > This release includes many bug fixes, as well as the Rocket Chat
> > > > Notification Connector.
> > > >
> > > > The release artifact can be downloaded from:
> > > > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-
> > manifoldcf-2.9
> > > >
> > > > There is also an svn tag at:
> > > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.9-RC2
> > > >
> > > > This also includes a fix for CONNECTORS-1477 and CONNECTORS-1479.
> > > >
> > > > Thanks!
> > > > Karl
> > > >
> > >
> >
>
>
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> https://www.open4dev.com
>

Re: [VOTE] Release Apache ManifoldCF 2.9, RC1

[Furkan KAMACI]

+1 from me.

Compiled project, ran tests and tested UI.

Kind Regards,
Furkan KAMACI

On Mon, Dec 18, 2017 at 5:30 PM, Piergiorgio Lucidi <piergior...@apache.org>
wrote:

> +1 from me.
>
> Ran tests and started a job using the UI with proprietary and standard
> example.
>
> PJ
>
> 2017-12-16 19:58 GMT+01:00 Karl Wright <daddy...@gmail.com>:
>
> > Please vote on whether to release Apache ManifoldCF 2.9, RC1.
> >
> > This release includes many bug fixes, as well as the Rocket Chat
> > Notification Connector.
> >
> > The release artifact can be downloaded from:
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.9
> >
> > There is also an svn tag at:
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.9-RC1
> >
> > This also includes a fix for CONNECTORS-1477 (mislabeled CONNECTORS-1474
> in
> > the CHANGES.txt file unfortunately).
> >
> > Thanks!
> > Karl
> >
>
>
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> https://www.open4dev.com
>

Re: Proposal for a brand new ManifoldCF website

[Furkan KAMACI]

Hi Piergiorgio,

We certainly need a prettier website for ManifoldCF. UI is so important and
people creates their first impressions when they touch our website. I would
like to help such effort.

By the way, we can consider this template too: https://cloudstack.apache.org

Kind Regards,
Furkan KAMACI

On Thu, Nov 16, 2017 at 11:10 AM, Piergiorgio Lucidi <piergior...@apache.org
> wrote:

> Hi guys,
>
> during the Open Source Summit Europe I received a lot of feedbacks related
> to our website.
>
> Taking a look at other Apache projects such as Spark[1] or OFBiz[2], it is
> clear that ManifoldCF needs a restyling for its own website. I think that a
> brand new website could help us for engaging more people in the community
> as users and also contributors giving the right perception of a stable and
> a working project.
>
> I had the opportunity to work and talk with some Apache members[3] and
> Sharan Foga from the OFBiz community proposed us to use the same website
> template [4].
> I know that it is a huge work but I think that if we try to follow some
> existent project in terms of how expose contents, we can achieve this goal
> in the right way without investing too much time.
>
> What do you think about this?
> Please let me know.
>
> Thanks.
>
> Cheers,
> PJ
>
> [1] - https://spark.apache.org/
> [2] - https://ofbiz.apache.org/
> [3] -
> https://www.open4dev.com/journal/2017/11/3/open-source-
> summit-europe-2017-wrap-up
> [4] - https://drive.google.com/open?id=16gKmmfHqP0oVYdr2-hHnoi2NtvCdIe0G
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> https://www.open4dev.com
>

Re: [ANNOUNCE] Please welcome Luis Cabaceira as a ManifoldCF committer

[Furkan KAMACI]

Congrats!

Kind Regards,
Furkan KAMACI


3 Eki 2017 Sal, saat 22:29 tarihinde Piergiorgio Lucidi <
piergior...@apache.org> şunu yazdı:

> Hi Luis,
>
> a warm welcome from Rome :)
>
> Very happy to strictly work with you!
>
> Cheers,
> PJ
>
> 2017-10-03 20:16 GMT+02:00 Karl Wright <daddy...@gmail.com>:
>
> > Luis works with Alfresco and has been spearheading efforts to use
> > ManifoldCF as a data migration tool.  Please extend him a warm welcome!
> >
> > - The ManifoldCF PMC
> >
>
>
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> http://www.open4dev.com
>

Re: [ANNOUNCE] Please welcome Julien Masseira as a ManifoldCF committer

[Furkan KAMACI]

Congrats!

Kind Regards,
Furkan KAMACI


3 Eki 2017 Sal, saat 22:31 tarihinde Piergiorgio Lucidi <
piergior...@apache.org> şunu yazdı:

> Hi Julien,
>
> a warm welcome from Italy :)
>
> Cheers,
> PJ
>
> 2017-10-03 20:14 GMT+02:00 Karl Wright <daddy...@gmail.com>:
>
> > Julien has been contributing to ManifoldCF by way of France Labs for
> quite
> > some time.  Please extend Julien a warm welcome!
> >
> > - The ManifoldCF PMC
> >
>
>
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> http://www.open4dev.com
>

Re: [ANNOUNCE] Please welcome Steph van Schalkwyk as a ManifoldCF committer

[Furkan KAMACI]

Congrats!

Kind Regards,
Furkan KAMACI


3 Eki 2017 Sal, saat 22:31 tarihinde Piergiorgio Lucidi <
piergior...@apache.org> şunu yazdı:

> Hi Steph,
>
> welcome to this project and hope to work with you soon!
>
> Cheers,
> PJ
>
> 2017-10-03 20:13 GMT+02:00 Karl Wright <daddy...@gmail.com>:
>
> > Steph has been contributing for many months towards a more robust
> > ElasticSearch output connector and is very committed to ManifoldCF.
> Please
> > extend a warm welcome!
> >
> > - The ManifoldCF PMC
> >
>
>
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> http://www.open4dev.com
>

Re: Re: [VOTE] Release Apache ManifoldCF 2.8.1, RC2

[Furkan KAMACI]

Certainly +1 from me.


6 Eyl 2017 Çar, saat 08:38 tarihinde Karl Wright  şunu
yazdı:

> Hello all, I need two more votes for this release.
>
> Karl
>
>
> On Tue, Sep 5, 2017 at 11:15 AM, Karl Wright  wrote:
>
> > Hi Ahmet,
> >
> > I did not update.  However, this is a point release meant to replace 2.8,
> > so I think it is acceptable to have the same files as the 2.8 release.
> >
> > Karl
> >
> >
> > On Tue, Sep 5, 2017 at 10:52 AM, Ahmet Arslan  >
> > wrote:
> >
> >>
> >>
> >> Hi Karl,
> >> I see that SHA extension still remains as .sha. I think it should be
> >> .sha512 with the new distribution policy.Did you used updated
> release.bat
> >> to create the release candidate?
> >> Thanks,Ahmet
> >>
> >>
> >>
> >>  On Tuesday, September 5, 2017, 10:04:17 AM GMT+3, Karl Wright <
> >> daddy...@gmail.com> wrote:
> >>
> >>
> >>
> >>
> >>
> >> Tested to be sure runzookeeper.bat works.
> >> User who needed the fix also notes the entire setup now working for him.
> >>
> >> +1 from me.
> >>
> >> Karl
> >>
> >>
> >> On Sat, Sep 2, 2017 at 11:33 AM, Karl Wright 
> wrote:
> >>
> >> > Hi all,
> >> >
> >> > As per the discussion yesterday, I've packaged up a ManifoldCF 2.8.1
> >> > release to address three problems found with MCF 2.8.  Please see
> >> > CONNECTORS-1450, CONNECTORS-1451, and CONNECTORS-1452.
> >> >
> >> > The point release candidate can be found at:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-man
> >> ifoldcf-2.8.1
> >> >
> >> > There is also a tag at:
> >> >
> >> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.8.1-RC2
> >> >
> >> > Note: RC1 differs from RC2 in that RC1 had the wrong version of the
> poi
> >> > jars.  There are no other changes.
> >> >
> >> > Thanks!!
> >> > Karl
> >> >
> >> >
> >>
> >>
> >
>

Re: Should we put out a point release to address CONNECTORS-1450?

[Furkan KAMACI]

Hi Fellows,

I think it should be fixed and we can point a release for it.

Kind Regards,
Furkan KAMACI

On Thu, Aug 31, 2017 at 4:17 PM, S <st...@remcam.net> wrote:

> I'm for a fix.
> Steph
>
>
> -Original Message-
> From: "Karl Wright" <daddy...@gmail.com>
> Sent: ‎31/‎08/‎2017 07:55
> To: "dev" <dev@manifoldcf.apache.org>
> Subject: Should we put out a point release to address CONNECTORS-1450?
>
> Essentially, all Tika extractions for Microsoft Office files will fail
> without a fix for this problem, so I think it's pretty severe.  What does
> everyone else think?
>
> Karl
>

Re: [ANNOUNCE] ManifoldCF 2.8 has been released

[Furkan KAMACI]

Congrats mates!

On Mon, Aug 21, 2017 at 12:21 PM, Piergiorgio Lucidi  wrote:

> Thank you all for improving the project with updated support with latest
> technologies and new connectors :)
>
> Great job!
>
> 2017-08-20 23:35 GMT+02:00 Ahmet Arslan :
>
> > Thanks to everyone who helped and contributed to making this release!
> >
> >
> > On Sunday, August 20, 2017, 9:29:58 PM GMT+3, Karl Wright <
> > daddy...@gmail.com> wrote:
> >
> > This release includes a new connector (Nuxeo) as well as numerous fixes
> and
> > improvements to other connectors.  Solr 6.x support and ElasticSearch 5.x
> > support have also been added.
> >
> > Please join me in congratulating the ManifoldCF team and the ManifoldCF
> > contributors for their invaluable assistance in pulling this release
> > together.
> >
> > Thanks!
> > Karl
> >
>
>
>
> --
> Piergiorgio Lucidi
> Technology Evangelist and Chief of Enterprise Information Management @
> Sourcesense
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> http://www.open4dev.com
>

Re: [VOTE] Release Apache ManifoldCF 2.8, RC0

[Furkan KAMACI]

+1 from me.


16 Ağu 2017 Çar, saat 21:52 tarihinde Antonio David Pérez Morales <
adperezmora...@gmail.com> şunu yazdı:

> Hi,
>
> Ran the tests and ran a job
>
> +1 from my side
>
> 2017-08-16 5:20 GMT+02:00 Shinichiro Abe :
>
> > Hi,
> >
> > Ran tests, unpacked the bin and ran a job.
> >
> > +1 from me.
> >
> > Shinichiro Abe
> >
> > 2017-08-15 18:08 GMT+09:00 Karl Wright :
> >
> > > Please vote on whether to release Apache ManifoldCF version 2.8, RC0.
> > >
> > > The release artifacts can be found at:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.8
> > >
> > > There is also a tag at:
> > >
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.8-RC0
> > >
> > > This release includes a new connector (for Nuxeo), as well as many
> > > significant bug
> > > fixes for the new UI and for many individual connectors.  Please check
> it
> > > out!
> > >
> > > Thanks,
> > >
> > > Karl
> > >
> >
>

Re: Dropbox Repository Connector

[Furkan KAMACI]

I've solved my problem. For the people who get same error should use access
token not request token.

On Wed, Jun 28, 2017 at 9:39 PM, Furkan KAMACI <furkankam...@gmail.com>
wrote:

> Actually, I've used oauth_token_secret as secret and oauth_token as key
> but didn't work.
>
> Btw, Dropbox says that today is planned as the last day to support the old
> API but they've postponed it for a couple of months.
>
> On Wed, Jun 28, 2017 at 9:17 PM, Furkan KAMACI <furkankam...@gmail.com>
> wrote:
>
>> Hi Folks,
>>
>> I test Dropbox repository connector but couldn't find secret and key (not
>> application one) due to old API is deprecated. Could you guide me?
>>
>> Kind Regards,
>> Furkan KAMACI
>>
>
>

Re: Dropbox Repository Connector

[Furkan KAMACI]

Actually, I've used oauth_token_secret as secret and oauth_token as key but
didn't work.

Btw, Dropbox says that today is planned as the last day to support the old
API but they've postponed it for a couple of months.

On Wed, Jun 28, 2017 at 9:17 PM, Furkan KAMACI <furkankam...@gmail.com>
wrote:

> Hi Folks,
>
> I test Dropbox repository connector but couldn't find secret and key (not
> application one) due to old API is deprecated. Could you guide me?
>
> Kind Regards,
> Furkan KAMACI
>

Dropbox Repository Connector

[Furkan KAMACI]

Hi Folks,

I test Dropbox repository connector but couldn't find secret and key (not
application one) due to old API is deprecated. Could you guide me?

Kind Regards,
Furkan KAMACI

[jira] [Commented] (CONNECTORS-699) Provide a script for OAuth registration for GoogleDrive connector?

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-699:
--

[~kwri...@metacarta.com] is there anything done related to this issue? 

> Provide a script for OAuth registration for GoogleDrive connector?
> --
>
> Key: CONNECTORS-699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: GoogleDrive connector
>Affects Versions: ManifoldCF 1.3
>Reporter: Karl Wright
>Assignee: Karl Wright
> Fix For: ManifoldCF next
>
>
> The GoogleDrive connector requires a context token.  In order to obtain that 
> context token, it is necessary to register the application against a central 
> server somewhere (which I believe is covered in the GoogleDrive end-user 
> documentation).  It may be helpful to provide a script which does this 
> instead; would make life potentially easier and could be extended for 
> SharePoint 2013 and others.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Proposal for adding Azure Content Storage connectors

[Furkan KAMACI]

Cool!

On Tue, Jun 27, 2017 at 4:36 PM, Karl Wright  wrote:

> I think this is a fine idea!
>
> Karl
>
>
> On Tue, Jun 27, 2017 at 8:44 AM, Piergiorgio Lucidi <
> piergior...@apache.org>
> wrote:
>
> > Hi,
> >
> > I would like to know what you think about adding two new connectors in
> the
> > project dedicated to crawl and migrate contents against the Azure Content
> > Storage.
> >
> > I could work on these new components:
> >
> >- an Azure Repository Connector for crawling contents
> >- an Azure Output Connector for migrating contents
> >
> >
> > Please let me know.
> > Thank you so much for any feedback.
> >
> > Cheers,
> > PJ
> >
> > --
> > Piergiorgio Lucidi
> > Technology Evangelist and Chief of Enterprise Information Management @
> > Sourcesense
> > Mentor / PMC Member / Committer @ Apache Software Foundation
> > Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> > Author and Technical Reviewer @ Packt Publishing
> > Technical Advisory Group Member @ Microsoft
> > Top Community Contributor @ Crafter
> > Project Leader / Committer @ JBoss
> > http://www.open4dev.com
> >
>

Exchange Repository Connector

[Furkan KAMACI]

Hi Team,

Currently we have a "Individual Email Repository Connection" which works on
IMAP, IMAP-SSL, POP3, or POP3-SSL.

However, I think that we should also have an Exchange Repository Connector
which works over Exchange Web Services (EWS). Current implementation has
some limitations and such a connector can overwhelm it.

For example, we should create individual connections for all e-mail
addresses if we want to index all e-mails within an Exchange Server. Also,
we should know all passwords of corresponding e-mail addresses. However, we
can access to other mailboxes with a user via EWS if that user authorised
to access it.

So, what do you think about it?

Kind Regards,
Furkan KAMACI

Re: [VOTE] Release Apache ManifoldCF 2.7.1, RC0

[Furkan KAMACI]

+1 from me.

I've run tests (I did not verify the signatures).

Kind Regards,
Furkan KAMACI

On Wed, May 10, 2017 at 12:58 AM, Karl Wright <daddy...@gmail.com> wrote:

> Any other voters?  We need one more.  It would be great to at least check
> signatures?
>
> Karl
>
>
> On Mon, May 8, 2017 at 1:21 PM, Karl Wright <daddy...@gmail.com> wrote:
>
> > Yes, that was intentional.  Patch releases are only meant to contain
> > critical fixes.
> >
> > Thanks,
> > Karl
> >
> >
> > On Mon, May 8, 2017 at 12:18 PM, Kishore Kumar <kishorejan...@live.com>
> > wrote:
> >
> >> Hi Karl,
> >>
> >> +1 from me.
> >>
> >> Able to upload a certificates to ManifoldCF, however, I couldn't find
> the
> >> updated index.jsp in which I made a change to load the latest mcf.js.
> >> https://github.com/apache/manifoldcf/commit/98d5b3a3b54aedff
> >> bae88019b41b7067f1171fe8
> >>
> >> If it's left intentional, I am fine.
> >>
> >> Thanks,
> >> KK
> >>
> >> -Original Message-
> >> From: Karl Wright [mailto:daddy...@gmail.com]
> >> Sent: 08 May 2017 01:42
> >> To: dev <dev@manifoldcf.apache.org>
> >> Subject: Re: [VOTE] Release Apache ManifoldCF 2.7.1, RC0
> >>
> >> I smoke-tested the release branch, after being sure to flush the Google
> >> Chrome buffers (see the CONNECTORS-1423 ticket for instructions), and it
> >> looked good for being able to upload certificates into the local
> keystore
> >> now for the SharePoint connector, at least.
> >>
> >> I did not verify signatures etc for the release candidate itself, but +1
> >> from me.
> >>
> >> Karl
> >>
> >>
> >> On Sun, May 7, 2017 at 10:58 AM, Karl Wright <daddy...@gmail.com>
> wrote:
> >>
> >> > Please vote on whether to release Apache ManifoldCF 2.7.1.  This
> >> > release contains fixes for CONNECTORS-1422 and CONNECTORS-1423.
> >> >
> >> > You can find the release at:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2
> .
> >> > 7.1
> >> >
> >> > There is also a tag at:
> >> >
> >> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.7.1-RC0
> >> >
> >> > Thanks,
> >> > Karl
> >> >
> >> >
> >>
> >
> >
>

Re: Should we have a 2.7.1 release?

[Furkan KAMACI]

+1 for new release.

On Sat, May 6, 2017 at 1:52 PM, Piergiorgio Lucidi 
wrote:

> Hi,
>
> I think that we should have this hotfix release.
> It seems critical for any new user that is starting to adopt ManifoldCF.
>
> Cheers,
> PJ
>
> 2017-05-06 0:07 GMT+02:00 Kishore Kumar :
>
> > Hi Karl,
> >
> > You are right, without this fix users will not be able to add a new
> > Certificate.
> > But if they have upgraded from a previous version with the certificates
> > already configured, then this won't be an issue for them.
> >
> > I would suggest to release a new version, because this will impact the
> new
> > users coming to ManifoldCF.
> >
> > My bad, I noticed this issue while back while I was working on the Web
> > Crawler connector, but ignored it assuming that the certificate that I
> was
> > using for testing was broken or a wrong certificate.
> >
> > Thanks,
> > KK
> >
> > -Original Message-
> > From: Karl Wright [mailto:daddy...@gmail.com]
> > Sent: 06 May 2017 03:31
> > To: dev 
> > Subject: Should we have a 2.7.1 release?
> >
> > See CONNECTORS-1423.  This appears to be serious enough because it makes
> > it impossible to configure several of our connectors.
> >
> > Thoughts?
> >
> > Karl
> >
>
>
>
> --
> Piergiorgio Lucidi
> Technology Evangelist @ Sourcesense
> Author and Technical Reviewer @ Packt Publishing
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Wiki Gardener / Forum Moderator / Certified Instructor, Engineer and
> Administrator @ Alfresco
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> Technology Advisory Team Member @ Microsoft
> http://www.open4dev.com
>

[jira] [Resolved] (CONNECTORS-1413) Code smell in equals implementation

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI resolved CONNECTORS-1413.
---
Resolution: Fixed

> Code smell in equals implementation
> ---
>
> Key: CONNECTORS-1413
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1413
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: CMIS connector
>Reporter: JC
>    Assignee: Furkan KAMACI
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1413.patch
>
>
> Hi
> In a recent snapshot, I've found a suspicious code in 
> connectors/cmis/connector/src/main/java/org/apache/manifoldcf/authorities/authorities/cmis/CmisAuthorityConnector.java
> {code}
> 402   public boolean equals(Object o)
> 403   {
> 404 if (!(o instanceof AuthorizationResponseDescription))
> 405   return false;
> 406 AuthorizationResponseDescription ard = 
> (AuthorizationResponseDescription)o;
> 407 return ard.userName.equals(userName) && 
> ard.endpoint.equals(endpoint) &&
> 408   repositoryId.equals(repositoryId);
> 409   }
> {code}
> In Line 408,  repositoryId.equals(repositoryId) should be  
> repositoryId.equals(*ard*.repositoryId)? This might be a trivial issue but 
> wanted to report just in case. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1413) Code smell in equals implementation

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1413:
---

r1791824

> Code smell in equals implementation
> ---
>
> Key: CONNECTORS-1413
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1413
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: CMIS connector
>Reporter: JC
>    Assignee: Furkan KAMACI
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1413.patch
>
>
> Hi
> In a recent snapshot, I've found a suspicious code in 
> connectors/cmis/connector/src/main/java/org/apache/manifoldcf/authorities/authorities/cmis/CmisAuthorityConnector.java
> {code}
> 402   public boolean equals(Object o)
> 403   {
> 404 if (!(o instanceof AuthorizationResponseDescription))
> 405   return false;
> 406 AuthorizationResponseDescription ard = 
> (AuthorizationResponseDescription)o;
> 407 return ard.userName.equals(userName) && 
> ard.endpoint.equals(endpoint) &&
> 408   repositoryId.equals(repositoryId);
> 409   }
> {code}
> In Line 408,  repositoryId.equals(repositoryId) should be  
> repositoryId.equals(*ard*.repositoryId)? This might be a trivial issue but 
> wanted to report just in case. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1413) Code smell in equals implementation

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1413:
---

r1791822

> Code smell in equals implementation
> ---
>
> Key: CONNECTORS-1413
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1413
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: CMIS connector
>Reporter: JC
>    Assignee: Furkan KAMACI
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1413.patch
>
>
> Hi
> In a recent snapshot, I've found a suspicious code in 
> connectors/cmis/connector/src/main/java/org/apache/manifoldcf/authorities/authorities/cmis/CmisAuthorityConnector.java
> {code}
> 402   public boolean equals(Object o)
> 403   {
> 404 if (!(o instanceof AuthorizationResponseDescription))
> 405   return false;
> 406 AuthorizationResponseDescription ard = 
> (AuthorizationResponseDescription)o;
> 407 return ard.userName.equals(userName) && 
> ard.endpoint.equals(endpoint) &&
> 408   repositoryId.equals(repositoryId);
> 409   }
> {code}
> In Line 408,  repositoryId.equals(repositoryId) should be  
> repositoryId.equals(*ard*.repositoryId)? This might be a trivial issue but 
> wanted to report just in case. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1413) Code smell in equals implementation

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1413:
---

Sure!

> Code smell in equals implementation
> ---
>
> Key: CONNECTORS-1413
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1413
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: CMIS connector
>Reporter: JC
>Assignee: Karl Wright
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1413.patch
>
>
> Hi
> In a recent snapshot, I've found a suspicious code in 
> connectors/cmis/connector/src/main/java/org/apache/manifoldcf/authorities/authorities/cmis/CmisAuthorityConnector.java
> {code}
> 402   public boolean equals(Object o)
> 403   {
> 404 if (!(o instanceof AuthorizationResponseDescription))
> 405   return false;
> 406 AuthorizationResponseDescription ard = 
> (AuthorizationResponseDescription)o;
> 407 return ard.userName.equals(userName) && 
> ard.endpoint.equals(endpoint) &&
> 408   repositoryId.equals(repositoryId);
> 409   }
> {code}
> In Line 408,  repositoryId.equals(repositoryId) should be  
> repositoryId.equals(*ard*.repositoryId)? This might be a trivial issue but 
> wanted to report just in case. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache ManifoldCF 2.7, RC1

[Furkan KAMACI]

+1 for releasing RC1

On Tue, Apr 18, 2017 at 9:22 PM, Karl Wright <daddy...@gmail.com> wrote:

> Can you clarify?  Are you +1 for releasing RC1, or are you +1 for spinning
> an RC2 with the fix for CONNECTORS-1412?
>
> Karl
>
>
> On Tue, Apr 18, 2017 at 2:20 PM, Furkan KAMACI <furkankam...@gmail.com>
> wrote:
>
> > I am +1 for releasing 2.7
> >
> > On Tue, Apr 18, 2017 at 8:53 PM, Karl Wright <daddy...@gmail.com> wrote:
> >
> > > Should we withdraw the RC?
> > > Karl
> > >
> > >
> > > On Tue, Apr 18, 2017 at 1:51 PM, Furkan KAMACI <furkankam...@gmail.com
> >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I've run different test cases which includes Email Connector. I've
> > seen a
> > > > bug and attached a patch for it: CONNECTORS-1412
> > > >
> > > > -0 for me.
> > > >
> > > > Kind Regards,
> > > > Furkan KAMACI
> > > >
> > > > On Tue, Apr 18, 2017 at 2:45 PM, Rafa Haro <rh...@apache.org> wrote:
> > > >
> > > > > Download the binary distribution, start the server, browse the new
> > UI,
> > > > > configure a couple of connectors of each type (just for testing the
> > UI)
> > > > and
> > > > > run a simple crawling over File System.
> > > > >
> > > > > +1 for me
> > > > >
> > > > > On Tue, Apr 18, 2017 at 10:22 AM Karl Wright <daddy...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Ran it again; it did much better, but still failed because the
> > > alfresco
> > > > > > nexus repo is down (it returns 500 errors).
> > > > > >
> > > > > > Karl
> > > > > >
> > > > > >
> > > > > > On Tue, Apr 18, 2017 at 4:12 AM, Karl Wright <daddy...@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > Jenkins is complaining about trunk.  And it appears it tried to
> > run
> > > > the
> > > > > > > job on a machine that did not have ant installed.  I'll have to
> > > > change
> > > > > > the
> > > > > > > config.
> > > > > > >
> > > > > > > Karl
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Apr 18, 2017 at 4:09 AM, Rafa Haro <rh...@apache.org>
> > > wrote:
> > > > > > >
> > > > > > >> It seems that Jenkins is complaining
> > > > > > >> El El mar, 18 abr 2017 a las 1:28, Karl Wright <
> > > daddy...@gmail.com>
> > > > > > >> escribió:
> > > > > > >>
> > > > > > >> > Ran standard tests.
> > > > > > >> > +1 from me.
> > > > > > >> >
> > > > > > >> > Karl
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > On Mon, Apr 17, 2017 at 10:46 AM, Karl Wright <
> > > daddy...@gmail.com
> > > > >
> > > > > > >> wrote:
> > > > > > >> >
> > > > > > >> > > Please vote on whether to release Apache ManifoldCF 2.7,
> > RC1.
> > > > > This
> > > > > > >> > > release has many major changes, including a new version of
> > > > Tika, a
> > > > > > new
> > > > > > >> > UI,
> > > > > > >> > > and major improvements to some connectors, e.g. the Email
> > > > > Connector.
> > > > > > >> > >
> > > > > > >> > > You can download the release from:
> > > > > > >> > >
> > > > > > >> > > https://dist.apache.org/repos/
> > dist/dev/manifoldcf/apache-man
> > > > > > >> ifoldcf-2.7
> > > > > > >> > >
> > > > > > >> > > There is also a release tag here:
> > > > > > >> > >
> > > > > > >> > > https://svn.apache.org/repos/
> asf/manifoldcf/tags/release-2.
> > > > 7-RC1
> > > > > > >> > >
> > > > > > >> > > Thanks,
> > > > > > >> > > Karl
> > > > > > >> > >
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Commented] (CONNECTORS-1413) Code smell in equals implementation

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1413:
---

Yes, you are right. [~kwri...@metacarta.com] I can commit my patch to trunk?

> Code smell in equals implementation
> ---
>
> Key: CONNECTORS-1413
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1413
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: CMIS connector
>Reporter: JC
>Assignee: Karl Wright
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1413.patch
>
>
> Hi
> In a recent snapshot, I've found a suspicious code in 
> connectors/cmis/connector/src/main/java/org/apache/manifoldcf/authorities/authorities/cmis/CmisAuthorityConnector.java
> {code}
> 402   public boolean equals(Object o)
> 403   {
> 404 if (!(o instanceof AuthorizationResponseDescription))
> 405   return false;
> 406 AuthorizationResponseDescription ard = 
> (AuthorizationResponseDescription)o;
> 407 return ard.userName.equals(userName) && 
> ard.endpoint.equals(endpoint) &&
> 408   repositoryId.equals(repositoryId);
> 409   }
> {code}
> In Line 408,  repositoryId.equals(repositoryId) should be  
> repositoryId.equals(*ard*.repositoryId)? This might be a trivial issue but 
> wanted to report just in case. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1413) Code smell in equals implementation

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1413:
--
Attachment: CONNECTORS-1413.patch

> Code smell in equals implementation
> ---
>
> Key: CONNECTORS-1413
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1413
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: CMIS connector
>Reporter: JC
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1413.patch
>
>
> Hi
> In a recent snapshot, I've found a suspicious code in 
> connectors/cmis/connector/src/main/java/org/apache/manifoldcf/authorities/authorities/cmis/CmisAuthorityConnector.java
> {code}
> 402   public boolean equals(Object o)
> 403   {
> 404 if (!(o instanceof AuthorizationResponseDescription))
> 405   return false;
> 406 AuthorizationResponseDescription ard = 
> (AuthorizationResponseDescription)o;
> 407 return ard.userName.equals(userName) && 
> ard.endpoint.equals(endpoint) &&
> 408   repositoryId.equals(repositoryId);
> 409   }
> {code}
> In Line 408,  repositoryId.equals(repositoryId) should be  
> repositoryId.equals(*ard*.repositoryId)? This might be a trivial issue but 
> wanted to report just in case. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1412) Email Job Fails if To Recipient is Not Specified

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1412:
---

r1791819

> Email Job Fails if To Recipient is Not Specified
> 
>
> Key: CONNECTORS-1412
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1412
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1412.patch
>
>
> Emails can be CC'ed without defining a To recipient. In such case, ManifoldCF 
> tries to run that line:
> {code:java}
> String[] toStr = new String[to.length];
> {code}
> which causes an error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache ManifoldCF 2.7, RC1

[Furkan KAMACI]

Hi,

I've run different test cases which includes Email Connector. I've seen a
bug and attached a patch for it: CONNECTORS-1412

-0 for me.

Kind Regards,
Furkan KAMACI

On Tue, Apr 18, 2017 at 2:45 PM, Rafa Haro <rh...@apache.org> wrote:

> Download the binary distribution, start the server, browse the new UI,
> configure a couple of connectors of each type (just for testing the UI) and
> run a simple crawling over File System.
>
> +1 for me
>
> On Tue, Apr 18, 2017 at 10:22 AM Karl Wright <daddy...@gmail.com> wrote:
>
> > Ran it again; it did much better, but still failed because the alfresco
> > nexus repo is down (it returns 500 errors).
> >
> > Karl
> >
> >
> > On Tue, Apr 18, 2017 at 4:12 AM, Karl Wright <daddy...@gmail.com> wrote:
> >
> > > Jenkins is complaining about trunk.  And it appears it tried to run the
> > > job on a machine that did not have ant installed.  I'll have to change
> > the
> > > config.
> > >
> > > Karl
> > >
> > >
> > > On Tue, Apr 18, 2017 at 4:09 AM, Rafa Haro <rh...@apache.org> wrote:
> > >
> > >> It seems that Jenkins is complaining
> > >> El El mar, 18 abr 2017 a las 1:28, Karl Wright <daddy...@gmail.com>
> > >> escribió:
> > >>
> > >> > Ran standard tests.
> > >> > +1 from me.
> > >> >
> > >> > Karl
> > >> >
> > >> >
> > >> > On Mon, Apr 17, 2017 at 10:46 AM, Karl Wright <daddy...@gmail.com>
> > >> wrote:
> > >> >
> > >> > > Please vote on whether to release Apache ManifoldCF 2.7, RC1.
> This
> > >> > > release has many major changes, including a new version of Tika, a
> > new
> > >> > UI,
> > >> > > and major improvements to some connectors, e.g. the Email
> Connector.
> > >> > >
> > >> > > You can download the release from:
> > >> > >
> > >> > > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-man
> > >> ifoldcf-2.7
> > >> > >
> > >> > > There is also a release tag here:
> > >> > >
> > >> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.7-RC1
> > >> > >
> > >> > > Thanks,
> > >> > > Karl
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

[jira] [Created] (CONNECTORS-1412) Email Job Fails if To Recipient is Not Specified

[Furkan KAMACI (JIRA)]

Furkan KAMACI created CONNECTORS-1412:
-

 Summary: Email Job Fails if To Recipient is Not Specified
 Key: CONNECTORS-1412
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1412
 Project: ManifoldCF
  Issue Type: Bug
  Components: Email connector
Affects Versions: ManifoldCF 2.6
Reporter: Furkan KAMACI
Assignee: Furkan KAMACI
 Fix For: ManifoldCF 2.8
 Attachments: CONNECTORS-1412.patch

Emails can be CC'ed without defining a To recipient. In such case, ManifoldCF 
tries to run that line:

{code:java}
String[] toStr = new String[to.length];
{code}

which causes an error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1412) Email Job Fails if To Recipient is Not Specified

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1412:
--
Attachment: CONNECTORS-1412.patch

> Email Job Fails if To Recipient is Not Specified
> 
>
> Key: CONNECTORS-1412
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1412
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1412.patch
>
>
> Emails can be CC'ed without defining a To recipient. In such case, ManifoldCF 
> tries to run that line:
> {code:java}
> String[] toStr = new String[to.length];
> {code}
> which causes an error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Help! Has anyone ever used log4j 2 before?

[Furkan KAMACI]

Hi Karl,

Just to double check: did you named properties file as log4j2.properties?

Kind Regards,
Furkan KAMACI

On Mon, Apr 17, 2017 at 12:48 PM, Karl Wright <daddy...@gmail.com> wrote:

> FWIW, it turns out that I could not get a .properties configuration to
> work.  But I was able to get an XML configuration to work, so I switched to
> that.
>
> Karl
>
>
> On Sun, Apr 16, 2017 at 8:45 AM, Karl Wright <daddy...@gmail.com> wrote:
>
> > Yes, of course.
> > Karl
> >
> > On Apr 16, 2017 8:15 AM, "Furkan KAMACI" <furkankam...@gmail.com> wrote:
> >
> >> Hi Karl,
> >>
> >> Did you check here:
> >> https://logging.apache.org/log4j/2.x/manual/migration.html
> >>
> >> Kind Regards,
> >> Furkan KAMACI
> >>
> >> On Sun, Apr 16, 2017 at 9:33 AM, Karl Wright <daddy...@gmail.com>
> wrote:
> >>
> >> > Hi all,
> >> >
> >> > I'm in the process of migrating MCF to log4j 2, but I am having a lot
> of
> >> > trouble getting it to work at all.  This is where things stand:
> >> >
> >> > (1) I had to change the name of our logging file from logging.ini to
> >> > logging.properties, because otherwise it attempts to interpret it as
> >> XML;
> >> >
> >> > (2) The format of the file has now changed; new properties are needed.
> >> I
> >> > tried to find examples of these online but failed to find any working
> >> > example.  Based on the documentation for log4j2, I worked up a guess
> at
> >> > what a simple logging.properties file would look like:
> >> >
> >> > >>>>>>
> >> > status=info
> >> > name=ManifoldCF
> >> > property.filename = logs/manifoldcf.log
> >> >
> >> > appender.file.type = File
> >> > appender.file.name = file
> >> > appender.file.fileName = logs/manifoldcf.log
> >> > appender.file.layout.type = PatternLayout
> >> > appender.file.pattern = %5p %d{ISO8601} (%t) - %m%n
> >> >
> >> > rootLogger.level = warn
> >> > rootLogger.appenderRef.file.ref = file
> >> > <<<<<<
> >> >
> >> > This, however, doesn't work; particularly, it fails to even create the
> >> log
> >> > file, although I have lock debugging turned on and we should be
> seeing a
> >> > lot of DEBUG logging events.
> >> >
> >> > There's a manual, of sorts, but it doesn't really even cover the
> >> > PropertiesConfigurator, I guess since it wasn't introduced until
> version
> >> > 2.4.  I've tried to roughly emulate the sample XML configurations in
> >> > properties but no luck.  Does anyone have a resource that they can
> >> point me
> >> > to here?
> >> >
> >> > Thanks!!
> >> > Karl
> >> >
> >>
> >
>

[jira] [Resolved] (CONNECTORS-1411) Attachment URL Template is Reset

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI resolved CONNECTORS-1411.
---
Resolution: Fixed

> Attachment URL Template is Reset
> 
>
> Key: CONNECTORS-1411
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1411
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1411.patch
>
>
> To reproduce the issue:
> 1) Create an e-mail repository connection.
> 2) Update attachment URL template.
> 3) Save connection.
> 4) Edit server information.
> Result: Attachment URL template is overridden to default. On the other hand 
> attachment URL template is not placed at view page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CONNECTORS-1410) Use Body as Content at Emails

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI resolved CONNECTORS-1410.
---
Resolution: Fixed

> Use Body as Content at Emails
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch, CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1411) Attachment URL Template is Reset

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1411:
---

r1791609

> Attachment URL Template is Reset
> 
>
> Key: CONNECTORS-1411
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1411
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1411.patch
>
>
> To reproduce the issue:
> 1) Create an e-mail repository connection.
> 2) Update attachment URL template.
> 3) Save connection.
> 4) Edit server information.
> Result: Attachment URL template is overridden to default. On the other hand 
> attachment URL template is not placed at view page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1411) Attachment URL Template is Reset

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1411:
--
Attachment: CONNECTORS-1411.patch

[~kwri...@metacarta.com] we should add this to 2.7 due to it is a bug.

> Attachment URL Template is Reset
> 
>
> Key: CONNECTORS-1411
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1411
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1411.patch
>
>
> To reproduce the issue:
> 1) Create an e-mail repository connection.
> 2) Update attachment URL template.
> 3) Save connection.
> 4) Edit server information.
> Result: Attachment URL template is overridden to default. On the other hand 
> attachment URL template is not placed at view page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CONNECTORS-1411) Attachment URL Template is Reset

[Furkan KAMACI (JIRA)]

Furkan KAMACI created CONNECTORS-1411:
-

 Summary: Attachment URL Template is Reset
 Key: CONNECTORS-1411
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1411
 Project: ManifoldCF
  Issue Type: Bug
  Components: Email connector
Affects Versions: ManifoldCF 2.6
Reporter: Furkan KAMACI
Assignee: Furkan KAMACI
 Fix For: ManifoldCF 2.7


To reproduce the issue:

1) Create an e-mail repository connection.
2) Update attachment URL template.
3) Save connection.
4) Edit server information.

Result: Attachment URL template is overridden to default. On the other hand 
attachment URL template is not placed at view page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Help! Has anyone ever used log4j 2 before?

[Furkan KAMACI]

Hi Karl,

Did you check here:
https://logging.apache.org/log4j/2.x/manual/migration.html

Kind Regards,
Furkan KAMACI

On Sun, Apr 16, 2017 at 9:33 AM, Karl Wright <daddy...@gmail.com> wrote:

> Hi all,
>
> I'm in the process of migrating MCF to log4j 2, but I am having a lot of
> trouble getting it to work at all.  This is where things stand:
>
> (1) I had to change the name of our logging file from logging.ini to
> logging.properties, because otherwise it attempts to interpret it as XML;
>
> (2) The format of the file has now changed; new properties are needed.  I
> tried to find examples of these online but failed to find any working
> example.  Based on the documentation for log4j2, I worked up a guess at
> what a simple logging.properties file would look like:
>
> >>>>>>
> status=info
> name=ManifoldCF
> property.filename = logs/manifoldcf.log
>
> appender.file.type = File
> appender.file.name = file
> appender.file.fileName = logs/manifoldcf.log
> appender.file.layout.type = PatternLayout
> appender.file.pattern = %5p %d{ISO8601} (%t) - %m%n
>
> rootLogger.level = warn
> rootLogger.appenderRef.file.ref = file
> <<<<<<
>
> This, however, doesn't work; particularly, it fails to even create the log
> file, although I have lock debugging turned on and we should be seeing a
> lot of DEBUG logging events.
>
> There's a manual, of sorts, but it doesn't really even cover the
> PropertiesConfigurator, I guess since it wasn't introduced until version
> 2.4.  I've tried to roughly emulate the sample XML configurations in
> properties but no luck.  Does anyone have a resource that they can point me
> to here?
>
> Thanks!!
> Karl
>

[jira] [Commented] (CONNECTORS-1405) Add Attachment Filenames Metadata To Email

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1405:
---

That's all for 2.7 :)

r1791603

> Add Attachment Filenames Metadata To Email
> --
>
> Key: CONNECTORS-1405
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1405
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1405.patch, CONNECTORS-1405.patch
>
>
> Filenames of attachments should be included as metadata.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1405) Add Attachment Filenames Metadata To Email

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1405:
--
Attachment: CONNECTORS-1405.patch

[~kwri...@metacarta.com] it seems that "filename" field may be confusing. I've 
updated it with ''attachmentname". Can you check my patch?

> Add Attachment Filenames Metadata To Email
> --
>
> Key: CONNECTORS-1405
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1405
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1405.patch, CONNECTORS-1405.patch
>
>
> Filenames of attachments should be included as metadata.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1410) Use Body as Content at Emails

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1410:
---

r1791548

> Use Body as Content at Emails
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch, CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1410) Use Body as Content at Emails

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1410:
--
Summary: Use Body as Content at Emails  (was: Binary Attachment Data as 
Plain Text at Email Content)

> Use Body as Content at Emails
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch, CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1410) Binary Attachment Data as Plain Text at Email Content

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1410:
--
Issue Type: Improvement  (was: Bug)

> Binary Attachment Data as Plain Text at Email Content
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch, CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1410) Binary Attachment Data as Plain Text at Email Content

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1410:
--
Attachment: CONNECTORS-1410.patch

> Binary Attachment Data as Plain Text at Email Content
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch, CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1410) Binary Attachment Data as Plain Text at Email Content

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1410:
---

[~kwri...@metacarta.com] Opps, nice catch! I let it to be searchable but 
accidentally removed  from BASIC_SEARCHABLE_ATTRIBUTES.

> Binary Attachment Data as Plain Text at Email Content
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1410) Binary Attachment Data as Plain Text at Email Content

[Furkan KAMACI (JIRA)]

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

Furkan KAMACI commented on CONNECTORS-1410:
---

[~kwri...@metacarta.com], you are right. Could you check my latest patch? I've 
tested it and works fine.

> Binary Attachment Data as Plain Text at Email Content
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1410) Binary Attachment Data as Plain Text at Email Content

[Furkan KAMACI (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Furkan KAMACI updated CONNECTORS-1410:
--
Attachment: CONNECTORS-1410.patch

> Binary Attachment Data as Plain Text at Email Content
> -
>
> Key: CONNECTORS-1410
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1410
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Furkan KAMACI
>    Assignee: Furkan KAMACI
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1410.patch, CONNECTORS-1410.patch, 
> CONNECTORS-1410.patch
>
>
> Previously, we were indexing e-mails and its attachments together. We changed 
> this logic with CONNECTORS-1375 as indexing e-mail and its attachments 
> separately.
> However, there is a problem. Content fields of emails which has attachment(s) 
> includes both body and attachments's binary content as plain text.
> As we index attachments separately, we can just index body as content instead 
> of appending email body and all attachments' binary data as plain text.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)