RE: [VOTE] Release Apache ManifoldCF 2.13, RC0

[Irindu Nugawela]

Hi Karl,
The URL does not direct to the artifact it gives me the following error when I 
try to visit the link 
Not Found
The requested URL /repos/dist/dev/manifoldcf/apache-manifoldcf-2.13. was not 
found on this server.
Please rectify the issue, Thank you very much

Sent from Mail for Windows 10

From: Karl Wright
Sent: Thursday, April 25, 2019 3:24 AM
To: dev
Subject: [VOTE] Release Apache ManifoldCF 2.13, RC0

Please vote on whether to release Apache ManifoldCF 2.13, RC0.  The release
artifact can be found at:
https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.13.
There is also a release tag at
https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.13-RC0.

This release contains primarily a redeveloped Jcifs connector, to work with
jcifs-ng, plus a modest number of bug fixes.

Karl

Build failed in Jenkins: ManifoldCF-mvn #706

[Apache Jenkins Server]

See 


Changes:

[kwright] Fix for CONNECTORS-1448.

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-eu2 (ubuntu trusty) in workspace 

Updating https://svn.apache.org/repos/asf/manifoldcf/trunk at revision 
'2019-04-25T01:24:11.322 +'
U framework/jetty-runner/pom.xml
U framework/pull-agent/pom.xml
U framework/authority-servlet/pom.xml
U framework/combined-service/pom.xml
U framework/agents/pom.xml
U framework/core/pom.xml
U framework/ui-core/pom.xml
U framework/api-service/pom.xml
U framework/script-engine/pom.xml
U framework/crawler-ui/pom.xml
U framework/less-compiler/pom.xml
U framework/connector-common/pom.xml
U framework/authority-service/pom.xml
U framework/pom.xml
U framework/api-servlet/pom.xml
U test-materials/alfresco-4-war/pom.xml
U test-materials/pom.xml
U build.xml
U connectors/opensearchserver/pom.xml
U connectors/solr/pom.xml
U connectors/filesystem/pom.xml
U connectors/hdfs/pom.xml
U connectors/jira/pom.xml
U connectors/rocketchat/pom.xml
U connectors/email/pom.xml
U connectors/searchblox/pom.xml
U connectors/pom.xml
U connectors/amazons3/pom.xml
U connectors/cmis/pom.xml
U connectors/nulloutput/pom.xml
U connectors/gts/pom.xml
U connectors/alfresco/pom.xml
U connectors/regexpmapper/pom.xml
U connectors/forcedmetadata/pom.xml
U connectors/wiki/pom.xml
U connectors/tikaservice/pom.xml
U connectors/sharepoint/pom.xml
U connectors/html-extractor/pom.xml
U connectors/dropbox/pom.xml
U connectors/gridfs/pom.xml
U connectors/ldap/pom.xml
U connectors/confluence/pom.xml
U connectors/nullauthority/pom.xml
U connectors/documentfilter/pom.xml
U connectors/mongodb/pom.xml
U connectors/tika/pom.xml
U connectors/slack/pom.xml
U connectors/webcrawler/pom.xml
U 
connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveHelpers.java
U 
connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveConnector.java
U connectors/jcifs/pom.xml
U connectors/jcifs/build.xml
U connectors/jcifs/proprietary-library-instructions.txt
U connectors/jcifs/lib-proprietary/README.txt
U connectors/alfresco-webscript/pom.xml
U connectors/nuxeo/pom.xml
U connectors/activedirectory/pom.xml
U connectors/contentlimiter/pom.xml
U connectors/nulltransformation/pom.xml
U connectors/jdbc/pom.xml
U connectors/amazoncloudsearch/pom.xml
U connectors/googledrive/pom.xml
U connectors/rss/pom.xml
U connectors/elasticsearch/pom.xml
U connectors/opennlp/pom.xml
U connectors/generic/pom.xml
U connectors/kafka/pom.xml
U CHANGES.txt
U pom.xml
 U.
At revision 1858081

[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
[ManifoldCF-mvn] $ /home/jenkins/tools/maven/apache-maven-3.2.1/bin/mvn 
-DskipTests=false -DskipITs=true clean -DskipTests -DskipITs install
[INFO] Scanning for projects...
Downloading: 
https://artifacts.alfresco.com/nexus/content/groups/public/org/alfresco/alfresco-platform-distribution/4.2.c/alfresco-platform-distribution-4.2.c.pom
4/9 KB   8/9 KB   9/9 KBDownloaded: 
https://artifacts.alfresco.com/nexus/content/groups/public/org/alfresco/alfresco-platform-distribution/4.2.c/alfresco-platform-distribution-4.2.c.pom
 (9 KB at 9.0 KB/sec)
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project  
( 
has 1 error
[ERROR] Non-parseable POM 
: 
expected > to finsh end tag not / from line 209 (position: TEXT seen 
...2.1.2 [Help 2]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/ModelParseException
Build step 'Invoke top-level Maven targets' marked build as failure
[locks-and-latches] Releasing all the locks

Re: Release 2.13 and CONNECTORS-1498

[Karl Wright]

I still would really like somebody to at least give it a try!

But if I don't hear by the end of the day, I'll go ahead and merge into
trunk and the release branch.

Karl


On Wed, Apr 24, 2019 at 11:49 AM Markus Schuch  wrote:

> Hi Karl.
>
> all windows shares in my reach were migrated to O365 services some months
> ago, so i am unfortunately unable to help here, sorry.
>
> IMHO we should ship because anyone using the abandoned jcifs based
> connector relies on vulnerable cifs protocols (if i am correct).
>
> Cheers
> Markus
>
>
> Am 24. April 2019 12:08:21 MESZ schrieb Karl Wright :
> >I'm still waiting for somebody to give the new Jcifs code a try before
> >spinning the release.  There apparently are plenty of people who want
> >us to
> >do work on the connector but who are unwilling to actually exercise it
> >when
> >that work is completed.
> >
> >I suppose I can integrate it and we can ship it.  Some people might be
> >surprised though. :-)
> >
> >Karl
> >
> >
> >On Mon, Apr 22, 2019 at 7:23 AM Karl Wright  wrote:
> >
> >> Hi all,
> >>
> >> It came to my attention last week that there's a new version of Jcifs
> >> available, which has some API changes and is thus not backwards
> >compatible
> >> with the old version.  But it also has significant new features
> >added.
> >>
> >> I updated the code for it in
> >> https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1498.
> > I
> >> haven't had opportunity to exercise it, so I'm hoping one of our
> >jcifs
> >> users will have a look with an eye towards including this new code in
> >the
> >> 2.13 release (for which I am about to push the button within the next
> >few
> >> days).  Any takers?
> >>
> >> Karl
> >>
> >>
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.

Re: Release 2.13 and CONNECTORS-1498

[Markus Schuch]

Hi Karl.

all windows shares in my reach were migrated to O365 services some months ago, 
so i am unfortunately unable to help here, sorry.

IMHO we should ship because anyone using the abandoned jcifs based connector 
relies on vulnerable cifs protocols (if i am correct).

Cheers
Markus


Am 24. April 2019 12:08:21 MESZ schrieb Karl Wright :
>I'm still waiting for somebody to give the new Jcifs code a try before
>spinning the release.  There apparently are plenty of people who want
>us to
>do work on the connector but who are unwilling to actually exercise it
>when
>that work is completed.
>
>I suppose I can integrate it and we can ship it.  Some people might be
>surprised though. :-)
>
>Karl
>
>
>On Mon, Apr 22, 2019 at 7:23 AM Karl Wright  wrote:
>
>> Hi all,
>>
>> It came to my attention last week that there's a new version of Jcifs
>> available, which has some API changes and is thus not backwards
>compatible
>> with the old version.  But it also has significant new features
>added.
>>
>> I updated the code for it in
>> https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1498.
> I
>> haven't had opportunity to exercise it, so I'm hoping one of our
>jcifs
>> users will have a look with an eye towards including this new code in
>the
>> 2.13 release (for which I am about to push the button within the next
>few
>> days).  Any takers?
>>
>> Karl
>>
>>

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Release 2.13 and CONNECTORS-1498

[Karl Wright]

I'm still waiting for somebody to give the new Jcifs code a try before
spinning the release.  There apparently are plenty of people who want us to
do work on the connector but who are unwilling to actually exercise it when
that work is completed.

I suppose I can integrate it and we can ship it.  Some people might be
surprised though. :-)

Karl


On Mon, Apr 22, 2019 at 7:23 AM Karl Wright  wrote:

> Hi all,
>
> It came to my attention last week that there's a new version of Jcifs
> available, which has some API changes and is thus not backwards compatible
> with the old version.  But it also has significant new features added.
>
> I updated the code for it in
> https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1498.  I
> haven't had opportunity to exercise it, so I'm hoping one of our jcifs
> users will have a look with an eye towards including this new code in the
> 2.13 release (for which I am about to push the button within the next few
> days).  Any takers?
>
> Karl
>
>

[jira] [Created] (CONNECTORS-1601) selector/regexp for which http error responses should/shouldn't be deleted

[roel goovaerts (JIRA)]

roel goovaerts created CONNECTORS-1601:
--

 Summary: selector/regexp for which http error responses 
should/shouldn't be deleted
 Key: CONNECTORS-1601
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1601
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Web connector
Affects Versions: ManifoldCF 2.12
Reporter: roel goovaerts


Would it be feasible to support a feature which lets the user control the 
deletions as an action response to certain error http codes?

In our use-case we would be ok with deleting 404 responses, but would need to 
keep 5xx's and 401's. As far as I was able to see in the UI and the source 
code, there is no operational distinction to make that would result in the 
prior description.



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