Re: My talk about Apache ManifoldCF at LinuxDay Rome 2012
I shared the presentation of my latest talk at LinuxDay 2012 here in Rome about Apache ManifoldCF on my website [1]. The talk has gone very well, I also added two sections in the presentation for introducing the concepts of repository and search server. I think that it helped very much :) I think that we have to add some informations on ManifoldCF website about all the improvements for the latest versions. At the end of the next week, after the Alfresco DevCon in Berlin, I can work on this task for updating the website ;) Piergiorgio [1] - http://www.open4dev.com/journal/2012/10/28/apache-manifoldcf-at-linuxday-slides.html 2012/10/15 Karl Wright daddy...@gmail.com Looks great - hope it goes well! I wish I could come but I *just* got back from Berlin yesterday, and I have responsibilities here thru Oct 31. Karl On Mon, Oct 15, 2012 at 4:17 AM, Piergiorgio Lucidi piergior...@apache.org wrote: Hi guys, I would like to share with you that at the next LinuxDay here in Rome I'll talk about Apache ManifoldCF, here my post: http://www.open4dev.com/journal/2012/10/15/apache-manifoldcf-at-linuxday.html Hope this helps ;) Cheers, Piergiorgio -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.comhttp://www.open4dev.com
Download links broken in the ManifoldCF website
Hi guys, I'm trying to download binaries from the download link in the website but it returns 404, here the broken link: http://www.apache.org/dyn/closer.cgi/manifoldcf/apache-manifoldcf-1.0.1-bin.tar.gz From the page: http://manifoldcf.apache.org/en_US/download.html#Latest+release+%28Apache+ManifoldCF+1.0.1%2C+2012+Oct+18%29 Do you have any ideas for solving this problem? Tomorrow I will keep a talk about ManifoldCF at the LinuxDay :-P Please let me know. Thank you. Piergiorgio -- Piergiorgio Lucidi http://www.open4dev.com
Re: Download links broken in the ManifoldCF website
Ok, now it works! ^__^ Probably a momentary issue. Piergiorgio 2012/10/26 Piergiorgio Lucidi piergior...@apache.org Hi guys, I'm trying to download binaries from the download link in the website but it returns 404, here the broken link: http://www.apache.org/dyn/closer.cgi/manifoldcf/apache-manifoldcf-1.0.1-bin.tar.gz From the page: http://manifoldcf.apache.org/en_US/download.html#Latest+release+%28Apache+ManifoldCF+1.0.1%2C+2012+Oct+18%29 Do you have any ideas for solving this problem? Tomorrow I will keep a talk about ManifoldCF at the LinuxDay :-P Please let me know. Thank you. Piergiorgio -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com
Re: New committer: Maciej Lizweski
Hi Maciej, a warm welcome from Rome! ^__^ Piergiorgio 2012/10/16 Karl Wright daddy...@gmail.com Please join me in welcoming Maciej as our newest committer and PMC member. Maciej brings with him knowledge of wikis, LDAP, and mail protocols, among many other skills. Welcome, Maciej! Karl -- Piergiorgio Lucidi http://www.open4dev.com
Re: [VOTE] Release Apache ManifoldCF 1.0.1, RC1
- executed integration tests - checked signatures - crawled a CMIS repository +1 from me PJ 2012/10/16 Karl Wright daddy...@gmail.com Downloaded artifacts, looked for leakage of maven target directories, and tried a maven build, which worked. +1 from me. Karl On Mon, Oct 15, 2012 at 7:34 PM, Karl Wright daddy...@gmail.com wrote: Vote +1 to release Apache ManifoldCF 1.0.1, RC1. You can find a tag at: https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.0.1-RC1 The artifact can be downloaded from: http://people.apache.org/~kwright/apache-manifoldcf-1.0.1 This patch release fixes the critical bug CONNECTORS-551. It also includes updated how-to-build-and-deploy documentation (CONNECTORS-546). Finally, it includes a fix for the maven build problem described in CONNECTORS-555. Thanks, Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Commented] (CONNECTORS-555) Alfresco maven build is broken
[
https://issues.apache.org/jira/browse/CONNECTORS-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475995#comment-13475995
]
Piergiorgio Lucidi commented on CONNECTORS-555:
---
Have you tried to remove that dependency from your local Maven repository and
re-run the install goal?
Alfresco maven build is broken
--
Key: CONNECTORS-555
URL: https://issues.apache.org/jira/browse/CONNECTORS-555
Project: ManifoldCF
Issue Type: Bug
Components: Build
Affects Versions: ManifoldCF 1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.1
The maven build steps:
{code}
mvn-bootstrap
mvn clean -DskipTests install
{code}
fail in the following way:
{code}
[ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
reso
lve dependencies for project
org.apache.manifoldcf:mcf-alfresco-connector:jar:1.
1-SNAPSHOT: Could not find artifact javax.activation:activation:jar:1.0.2 in
alf
resco-release
(https://artifacts.alfresco.com/nexus/content/repositories/release
s) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit
ch.
[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
rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :mcf-alfresco-connector
C:\wip\mcf\trunk
{code}
It looks like there is a missing dependency we may need. I think
activation.jar was there before, not sure what happened to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
My talk about Apache ManifoldCF at LinuxDay Rome 2012
Hi guys, I would like to share with you that at the next LinuxDay here in Rome I'll talk about Apache ManifoldCF, here my post: http://www.open4dev.com/journal/2012/10/15/apache-manifoldcf-at-linuxday.html Hope this helps ;) Cheers, Piergiorgio -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Commented] (CONNECTORS-555) Alfresco maven build is broken
[
https://issues.apache.org/jira/browse/CONNECTORS-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476317#comment-13476317
]
Piergiorgio Lucidi commented on CONNECTORS-555:
---
I reproduced this issue removing all the dependencies of javax.activation from
my local repository and removing any specific settings in the settings.xml of
Maven.
But I noticed that, during the execution of the command mvn clean install, the
CMIS Connector uses the same version of activation (1.0.2) and it was
successfully downloaded from the standard Maven repo:
{code}
Downloaded:
http://repo.maven.apache.org/maven2/javax/activation/activation/1.0.2/activation-1.0.2.pom
(776 B at 1.5 KB/sec)
{code}
It sounds strange...
Alfresco maven build is broken
--
Key: CONNECTORS-555
URL: https://issues.apache.org/jira/browse/CONNECTORS-555
Project: ManifoldCF
Issue Type: Bug
Components: Build
Affects Versions: ManifoldCF 1.0, ManifoldCF 1.0.1, ManifoldCF 1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0.1
The maven build steps:
{code}
mvn-bootstrap
mvn clean -DskipTests install
{code}
fail in the following way:
{code}
[ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
reso
lve dependencies for project
org.apache.manifoldcf:mcf-alfresco-connector:jar:1.
1-SNAPSHOT: Could not find artifact javax.activation:activation:jar:1.0.2 in
alf
resco-release
(https://artifacts.alfresco.com/nexus/content/repositories/release
s) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit
ch.
[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
rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :mcf-alfresco-connector
C:\wip\mcf\trunk
{code}
It looks like there is a missing dependency we may need. I think
activation.jar was there before, not sure what happened to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [PROPOSAL] Release a ManifoldCF 1.0.1 release
+1 from me PJ 2012/10/9 Karl Wright daddy...@gmail.com Hi folks, Due to the potential severity of CONNECTORS-551, I think it might be a good idea to release a ManifoldCF 1.0.1 release which contains the fix for this ticket. Please can I have a show of hands as to whether people agree that this is serious enough to warrant such a release. Thanks! Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Created] (CONNECTORS-549) Wrong credentials not correctly managed by CMIS Connector
Piergiorgio Lucidi created CONNECTORS-549:
-
Summary: Wrong credentials not correctly managed by CMIS Connector
Key: CONNECTORS-549
URL: https://issues.apache.org/jira/browse/CONNECTORS-549
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0
If you try to register a CMIS Connection with wrong credentials the
CmisPermissionDeniedException is not managed, the UI remain without any output
and it returns the following exception in the log file:
{code}
84334 [qtp1595252236-192] WARN org.eclipse.jetty.servlet.ServletHandler -
/mcf-crawler-ui/execute.jsp
org.apache.jasper.JasperException: An exception occurred processing JSP page
/viewconnection.jsp at line 108
105:{
106:try
107:{
108:connectionStatus = c.check();
109:}
110:finally
111:{
Stacktrace:
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:430)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:288)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:115)
at
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:709)
at
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:680)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:392)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:349)
at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
at
org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224
Re: [VOTE] Release Apache ManifoldCF 1.0, RC6
-1 from me. I found an issue on the CMIS Connector (CONNECTORS-549), I'm committing the patch to fix the problem. We need another RC. Piergiorgio 2012/9/28 Karl Wright daddy...@gmail.com Please vote +1 to release ManifoldCF 1.0, RC6. The release artifact can be found at: http://people.apache.org/~kwright/apache-manifoldcf-1.0 There is also an SVN tag at: https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.0-RC6 Fixes since RC5: CONNECTORS-547 CONNECTORS-548 (documentation fix) Fixes since RC4: CONNECTORS-545 Fixes since RC3: CONNECTORS-544 -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Resolved] (CONNECTORS-549) Wrong credentials not correctly managed by CMIS Connector
[
https://issues.apache.org/jira/browse/CONNECTORS-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-549.
---
Resolution: Fixed
r1392006.
Wrong credentials not correctly managed by CMIS Connector
-
Key: CONNECTORS-549
URL: https://issues.apache.org/jira/browse/CONNECTORS-549
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0
If you try to register a CMIS Connection with wrong credentials the
CmisPermissionDeniedException is not managed, the UI remain without any
output and it returns the following exception in the log file:
{code}
84334 [qtp1595252236-192] WARN org.eclipse.jetty.servlet.ServletHandler -
/mcf-crawler-ui/execute.jsp
org.apache.jasper.JasperException: An exception occurred processing JSP page
/viewconnection.jsp at line 108
105: {
106: try
107: {
108: connectionStatus = c.check();
109: }
110: finally
111: {
Stacktrace:
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:430)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:288)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:115)
at
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:709)
at
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:680)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:392)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:349)
at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
at
org.eclipse.jetty.server.HttpConnection$RequestHandler.content
Re: [VOTE] Release Apache ManifoldCF 1.0, RC7
+1 from me: - checked signatures - crawling against a CMIS repository - tried to build using Maven and Ant Piergiorgio 2012/9/30 Karl Wright daddy...@gmail.com Please vote +1 to release ManifoldCF 1.0, RC7. The release artifact can be found at: http://people.apache.org/~kwright/apache-manifoldcf-1.0 There is also an SVN tag at: https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.0-RC7 Fixes since RC6: CONNECTORS-549 Fixes since RC5: CONNECTORS-547 CONNECTORS-548 (documentation fix) Fixes since RC4: CONNECTORS-545 Fixes since RC3: CONNECTORS-544 -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Created] (CONNECTORS-538) Maven build broken on SharePoint Connector
Piergiorgio Lucidi created CONNECTORS-538:
-
Summary: Maven build broken on SharePoint Connector
Key: CONNECTORS-538
URL: https://issues.apache.org/jira/browse/CONNECTORS-538
Project: ManifoldCF
Issue Type: Bug
Components: Build, SharePoint connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Trying to execute the maven build, it returns the following exception:
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 23.103s
[INFO] Finished at: Mon Sep 24 15:53:10 CEST 2012
[INFO] Final Memory: 9M/486M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java (default) on project
mcf-sharepoint-connector: Execution default of goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java failed: A required class
was missing while executing
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java:
org/apache/axis/wsdl/WSDL2Java
[ERROR] -
[ERROR] realm =pluginorg.codehaus.mojo:axistools-maven-plugin:1.4
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/mojo/axistools-maven-plugin/1.4/axistools-maven-plugin-1.4.jar
[ERROR] urls[1] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-compiler-api/1.5.3/plexus-compiler-api-1.5.3.jar
[ERROR] urls[2] =
file:/Users/piergiorgiolucidi/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[3] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] urls[4] =
file:/Users/piergiorgiolucidi/.m2/repository/axis/axis/1.4/axis-1.4.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -:
org.apache.axis.wsdl.WSDL2Java
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-538) Maven build broken on SharePoint Connector
[
https://issues.apache.org/jira/browse/CONNECTORS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-538.
---
Resolution: Fixed
r1389389.
Maven build broken on SharePoint Connector
--
Key: CONNECTORS-538
URL: https://issues.apache.org/jira/browse/CONNECTORS-538
Project: ManifoldCF
Issue Type: Bug
Components: Build, SharePoint connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0
Original Estimate: 1h
Remaining Estimate: 1h
Trying to execute the maven build, it returns the following exception:
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 23.103s
[INFO] Finished at: Mon Sep 24 15:53:10 CEST 2012
[INFO] Final Memory: 9M/486M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java (default) on project
mcf-sharepoint-connector: Execution default of goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java failed: A required
class was missing while executing
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java:
org/apache/axis/wsdl/WSDL2Java
[ERROR] -
[ERROR] realm =pluginorg.codehaus.mojo:axistools-maven-plugin:1.4
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/mojo/axistools-maven-plugin/1.4/axistools-maven-plugin-1.4.jar
[ERROR] urls[1] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-compiler-api/1.5.3/plexus-compiler-api-1.5.3.jar
[ERROR] urls[2] =
file:/Users/piergiorgiolucidi/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[3] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] urls[4] =
file:/Users/piergiorgiolucidi/.m2/repository/axis/axis/1.4/axis-1.4.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -:
org.apache.axis.wsdl.WSDL2Java
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache ManifoldCF 1.0, RC1
I found a problem building the SharePoint connector with Maven (CONNECTORS-538), but I resolved this issue. I tested other functionalities and it seems all ok. So I think that if we build another RC, this time it could be ok :) Piergiorgio 2012/9/23 Karl Wright daddy...@gmail.com Examined the distribution for leakage of files that shouldn't be there, ran ant rat-sources, and ran all tests. +1 from me. Karl On Fri, Sep 21, 2012 at 3:48 PM, Karl Wright daddy...@gmail.com wrote: Please vote +1 to release ManifoldCF 1.0, RC1. The release artifact can be found at: http://people.apache.org/~kwright/apache-manifoldcf-1.0 There is also an SVN tag at: https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.0-RC1 Fixes since RC0: CONNECTORS-532 CONNECTORS-533 CONNECTORS-536 CONNECTORS-537 Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Created] (CONNECTORS-527) Error during CMIS ingestion of nodes without binary content
Piergiorgio Lucidi created CONNECTORS-527:
-
Summary: Error during CMIS ingestion of nodes without binary
content
Key: CONNECTORS-527
URL: https://issues.apache.org/jira/browse/CONNECTORS-527
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 0.7
In case of some nodes in the CMIS repository don't have binary stream, the
connector returns:
{code}
FATAL 2012-09-13 10:05:14,961 (Worker thread '1') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1070)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-525) Upgrade to OpenCMIS 0.7.0
[ https://issues.apache.org/jira/browse/CONNECTORS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-525. --- Resolution: Fixed r1384250. I have updated the scripts for building the lib folder. But now we need to release a new lib package ready to download, because now with this new version of OpenCMIS we have to remove these dependencies: jsr181-api-1.0-MR1 and jsr250-api-1.0. Upgrade to OpenCMIS 0.7.0 - Key: CONNECTORS-525 URL: https://issues.apache.org/jira/browse/CONNECTORS-525 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.7 Original Estimate: 2h Remaining Estimate: 2h We should upgrade CMIS Connector with the latest version of the OpenCMIS library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Winding down the 0.7 release, already??
+1 from me to start releasing the next version as 1.0. Taking a look at the current algorithm used by Maven for comparing versions [1], and at the Versioning page [2], I don't see any problem. Piergiorgio [1] - http://maven.apache.org/ref/3.0.4/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html [2] - http://docs.codehaus.org/display/MAVEN/Versioning 2012/9/13 Karl Wright daddy...@gmail.com The more I think about this, the more I think we may well be able to segregate ManifoldCF into major releases over time. Some of the very large tickets (for example, multi-server crawling) will almost certainly have a big impact on practically everything ManifoldCF does. I propose, then, that our major releases coincide with these very significant framework changes. That would imply that we can continue to have 0.xxx releases for quite some time, but since we did not plan on such an arrangement in advance, and since we want tools like Maven to work with our version numbers, I propose that we begin the 1.xxx series of releases right now, in this current release. Furthermore, we would include a minor level for patch releases in each version number. For example: 1.0.0 - release on Sept 30 1.1.0 - release on December 31 etc. The only question I have is what will Maven's version comparison logic do when it sees a version like this: 1.17.0 Hopefully it will recognize that this is a higher version than 1.2.0? Mavenistas, what say you? If Maven doesn't work right with this, we'd want to reserve digits in advance, e.g. 1.000.0 1.001.0 Karl On Wed, Sep 5, 2012 at 2:07 PM, Karl Wright daddy...@gmail.com wrote: I don't think there are any hard rules about what constitutes a 1.0 release, except perhaps some subjective measure of completeness, and some measure of backwards compatibility support. For example, Lucene insures that every major release number (3.x, 4.x) are index-compatible. I don't know what the equivalent major release equivalent would be for ManifoldCF. We have a mature database schema which self-upgrades, so that is not going to work in the same way as Lucene indexes. We *could* just keep counting: 0.7, 0.8. 0.9, 0.10, 0.11 etc. But that gets cumbersome too. Karl On Wed, Sep 5, 2012 at 5:44 AM, Piergiorgio Lucidi piergior...@apache.org wrote: Taking a look at all the recent fixes, I think that we could release a new version of ManifoldCF because there are many improvements: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+CONNECTORS+AND+fixVersion+%3D+%22ManifoldCF+0.7%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide I don't know what rules are defined for calling it as 1.0, but in the meanwhile we could release a 0.7 version. Personally I think that this new release could be named 1.0, but this is my feeling :) Piergiorgio 2012/8/27 Karl Wright daddy...@gmail.com Hi Folks, It's already time to start winding down the 0.7 release. Before this is done, I think we need the following: (1) Voting on the current outstanding SharePoint-2007 plugin release. Still need 2 votes. (2) Completion of, and voting on the new SharePoint-2010 plugin release. (3) Completion of all outstanding tickets marked Fix in ManifoldCF 0.7. I'd also like to explore what the criteria should be for calling a release 1.0. It seems to me that Jukka and others might have an idea of when this would be appropriate. Does anyone have any thoughts on this matter? Thanks, Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com
Re: [VOTE] Release Apache ManifoldCF Sharepoint 2010 plugin 0.1, RC1
We have just finishing crawling my SharePoint 2010 instance correctly :) +1 from me. Piergiorgio 2012/9/10 Karl Wright daddy...@gmail.com Piergiorgio and I got things working on his box, so +1 from me. On Sun, Sep 9, 2012 at 12:52 PM, Karl Wright daddy...@gmail.com wrote: Please vote +1 if you think the SharePoint 2010 plugin is ready for release. Tag in the usual place ( https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2010/tags/release-0.1-RC1 ). Artifact at http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2010-plugin-0.1 . Fixed: Pagination handling Thanks, Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Comment Edited] (CONNECTORS-519) maven build of mcf-test-materials/mcf-alfresco-war-test fails
[
https://issues.apache.org/jira/browse/CONNECTORS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13450698#comment-13450698
]
Piergiorgio Lucidi edited comment on CONNECTORS-519 at 9/8/12 2:13 AM:
---
Fixed also the URL of the Alfresco Maven repository in the Ant script: now it
is invoked in HTTPS (r1382060).
was (Author: piergiorgioluc...@gmail.com):
Fixed also the URL in the Ant script: now it is invoked in HTTPS (r1382060).
maven build of mcf-test-materials/mcf-alfresco-war-test fails
-
Key: CONNECTORS-519
URL: https://issues.apache.org/jira/browse/CONNECTORS-519
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector, Build
Environment: Mac OS X Version 10.7.4
java version 1.6.0_33
Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.4, arch: x86_64, family: mac
Reporter: Ahmet Arslan
Assignee: Piergiorgio Lucidi
Labels: alfresco-war-test, test-materials,
Fix For: ManifoldCF 0.7
Attachments: CONNECTORS-519.patch
When I try mvn clean install on trunk, I get the following error:
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] ManifoldCF SUCCESS [2.736s]
[INFO] ManifoldCF - Framework SUCCESS [0.074s]
[INFO] ManifoldCF - Framework - Core . SUCCESS [7.149s]
[INFO] ManifoldCF - Framework - UI Core .. SUCCESS [2.686s]
[INFO] ManifoldCF - Framework - Agents ... SUCCESS [18.703s]
[INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [21.628s]
[INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.355s]
[INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.411s]
[INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.314s]
[INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.042s]
[INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [2.889s]
[INFO] ManifoldCF - Framework - Script Engine SUCCESS [3.546s]
[INFO] ManifoldCF - Connectors ... SUCCESS [0.032s]
[INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.479s]
[INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [16.125s]
[INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.766s]
[INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [2.368s]
[INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.855s]
[INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.345s]
[INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.245s]
[INFO] ManifoldCF - Connectors - RSS . SUCCESS [3.012s]
[INFO] ManifoldCF - Connectors - SharePoint .. SUCCESS [12.172s]
[INFO] ManifoldCF - Connectors - Solr SUCCESS [1.864s]
[INFO] ManifoldCF - Connectors - Web . SUCCESS [3.292s]
[INFO] ManifoldCF - Connectors - CMIS SUCCESS [17.579s]
[INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [1.511s]
[INFO] ManifoldCF - Connectors - Wiki SUCCESS [16.313s]
[INFO] ManifoldCF - Connectors - Alfresco SUCCESS [16.978s]
[INFO] ManifoldCF - Connectors - ElasticSearch ... SUCCESS [2.101s]
[INFO] ManifoldCF - Test materials ... SUCCESS [0.020s]
[INFO] ManifoldCF - Test Materials - Alfresco WAR FAILURE [4.305s]
[INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
[INFO] ManifoldCF - Tests SKIPPED
[INFO] ManifoldCF - Test - ElasticSearch . SKIPPED
[INFO] ManifoldCF - Test - Alfresco .. SKIPPED
[INFO] ManifoldCF - Test - Wiki .. SKIPPED
[INFO] ManifoldCF - Test - CMIS .. SKIPPED
[INFO] ManifoldCF - Test - Filesystem SKIPPED
[INFO] ManifoldCF - Test - Sharepoint SKIPPED
[INFO] ManifoldCF - Test - RSS ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO
Re: [WITHDRAW][VOTE] Release Apache ManifoldCF SharePoint 2010 plugin 0.1 RC0
I have tried now the latest code and now the crawling process is terminating correctly without any exception. But I noticed that when the job is running, the total number of documents are correctly shown, and you can see that this number is incrementing gradually until the end of the job. But at the end of the job the number of documents shown in the UI returns a value equals to the number of libraries that you have configured. In the document history I only see three libraries shown in the Document Status view: - / - /My Custom Library 1// - /My Custom Library 2// Is this correct? Hope this helps. Piergiorgio 2012/9/6 Karl Wright daddy...@gmail.com I also just updated the plugin at sharepoint-2010/trunk to precisely follow a Microsoft example I found. Could you give this a try as well? Karl On Thu, Sep 6, 2012 at 5:08 PM, Karl Wright daddy...@gmail.com wrote: Thanks for trying this. Just as a check I increased the number of documents that will be requested on the connector side to 1. If you synch up trunk and try again, it should give me an idea whether the failing logic is on the connector side or the server side. (I suspect it is still the server side, which means that SharePoint's pagination is not working, but let's confirm that.) Thanks, Karl On Thu, Sep 6, 2012 at 4:19 PM, Ahmet Arslan iori...@yahoo.com wrote: I checked in a fix for the pagination issue in integration/sharepoint-2010/trunk. Care to build the plugin, deploy it, and let me know if it works now? Hi, svnversion 1381729 still index 1000 docs. Documents: 1002 Active: 0 Processed: 1002 Ahmet -- Piergiorgio Lucidi http://www.open4dev.com
Re: [WITHDRAW][VOTE] Release Apache ManifoldCF SharePoint 2010 plugin 0.1 RC0
I tried now upgrading the plugin on SharePoint and rebuilding the connector from the trunk but it returns me this exception: ERROR 2012-09-06 20:20:00,993 (Worker thread '41') - Exception tossed: Internal error: Relative path 'Library Custom/actions-article-v2.pdf' was expected to start with '/my/personal/administrator/demosite' org.apache.manifoldcf.core.interfaces.ManifoldCFException: Internal error: Relative path 'Library Custom/actions-article-v2.pdf' was expected to start with '/my/personal/administrator/demosite' at org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:655) at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:1303) at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561) It seems that there is an issue about the URL again. Hope this helps. Piergiorgio 2012/9/6 Karl Wright daddy...@gmail.com I checked in a fix for the pagination issue in integration/sharepoint-2010/trunk. Care to build the plugin, deploy it, and let me know if it works now? Karl On Thu, Sep 6, 2012 at 1:26 PM, Karl Wright daddy...@gmail.com wrote: I conclude that the plugin is not handling paging properly - there's no other explanation. So I am canceling the vote and will try to check in a fix. Karl On Thu, Sep 6, 2012 at 1:11 PM, Karl Wright daddy...@gmail.com wrote: It looks like two problems here. First, it looks like Solr is throwing a 500 error for at least one of the documents in your set. However, the fact that you only get 1000 documents indexed also shows that the code is still broken in some way. I will check into whether this looks like a problem in the connector or in the plugin. Karl On Thu, Sep 6, 2012 at 1:06 PM, Ahmet Arslan iori...@yahoo.com wrote: Hi Karl, With a document library that 7,888 items, I setup a crawl with mcf-trunk. Sometimes I get this exception : Error: Repeated service interruptions - failure processing document: Ingestion HTTP error code 500 If i don't get exception only 1000 docs are indexed. ERROR 2012-09-06 19:55:13,587 (Worker thread '30') - Exception tossed: Repeated service interruptions - failure processing document: Ingestion HTTP error code 500 org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service interruptions - failure processing document: Ingestion HTTP error code 500 at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:585) Caused by: org.apache.manifoldcf.core.interfaces.ManifoldCFException: Ingestion HTTP error code 500 at org.apache.manifoldcf.agents.output.solr.HttpPoster$IngestThread.run(HttpPoster.java:1386) Ahmet --- On Wed, 9/5/12, Karl Wright daddy...@gmail.com wrote: From: Karl Wright daddy...@gmail.com Subject: [VOTE] Release Apache ManifoldCF SharePoint 2010 plugin 0.1 RC0 To: dev dev@manifoldcf.apache.org Date: Wednesday, September 5, 2012, 11:52 PM Vote +1 if you think the Apache ManifoldCF SharePoint 2010 plugin 0.1 RC0 is ready for release. The release artifact can be found at: http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2010-plugin-0.1 . There is also a release tag at: https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2010/tags/release-0.1-RC0 Karl -- Piergiorgio Lucidi http://www.open4dev.com
Re: Winding down the 0.7 release, already??
Taking a look at all the recent fixes, I think that we could release a new version of ManifoldCF because there are many improvements: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+CONNECTORS+AND+fixVersion+%3D+%22ManifoldCF+0.7%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide I don't know what rules are defined for calling it as 1.0, but in the meanwhile we could release a 0.7 version. Personally I think that this new release could be named 1.0, but this is my feeling :) Piergiorgio 2012/8/27 Karl Wright daddy...@gmail.com Hi Folks, It's already time to start winding down the 0.7 release. Before this is done, I think we need the following: (1) Voting on the current outstanding SharePoint-2007 plugin release. Still need 2 votes. (2) Completion of, and voting on the new SharePoint-2010 plugin release. (3) Completion of all outstanding tickets marked Fix in ManifoldCF 0.7. I'd also like to explore what the criteria should be for calling a release 1.0. It seems to me that Jukka and others might have an idea of when this would be appropriate. Does anyone have any thoughts on this matter? Thanks, Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Resolved] (CONNECTORS-519) maven build of mcf-test-materials/mcf-alfresco-war-test fails
[
https://issues.apache.org/jira/browse/CONNECTORS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-519.
---
Resolution: Fixed
Resolved in r1381277.
maven build of mcf-test-materials/mcf-alfresco-war-test fails
-
Key: CONNECTORS-519
URL: https://issues.apache.org/jira/browse/CONNECTORS-519
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector, Build
Environment: Mac OS X Version 10.7.4
java version 1.6.0_33
Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.4, arch: x86_64, family: mac
Reporter: Ahmet Arslan
Assignee: Piergiorgio Lucidi
Labels: alfresco-war-test, test-materials,
Fix For: ManifoldCF 0.7
Attachments: CONNECTORS-519.patch
When I try mvn clean install on trunk, I get the following error:
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] ManifoldCF SUCCESS [2.736s]
[INFO] ManifoldCF - Framework SUCCESS [0.074s]
[INFO] ManifoldCF - Framework - Core . SUCCESS [7.149s]
[INFO] ManifoldCF - Framework - UI Core .. SUCCESS [2.686s]
[INFO] ManifoldCF - Framework - Agents ... SUCCESS [18.703s]
[INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [21.628s]
[INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.355s]
[INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.411s]
[INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.314s]
[INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.042s]
[INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [2.889s]
[INFO] ManifoldCF - Framework - Script Engine SUCCESS [3.546s]
[INFO] ManifoldCF - Connectors ... SUCCESS [0.032s]
[INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.479s]
[INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [16.125s]
[INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.766s]
[INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [2.368s]
[INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.855s]
[INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.345s]
[INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.245s]
[INFO] ManifoldCF - Connectors - RSS . SUCCESS [3.012s]
[INFO] ManifoldCF - Connectors - SharePoint .. SUCCESS [12.172s]
[INFO] ManifoldCF - Connectors - Solr SUCCESS [1.864s]
[INFO] ManifoldCF - Connectors - Web . SUCCESS [3.292s]
[INFO] ManifoldCF - Connectors - CMIS SUCCESS [17.579s]
[INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [1.511s]
[INFO] ManifoldCF - Connectors - Wiki SUCCESS [16.313s]
[INFO] ManifoldCF - Connectors - Alfresco SUCCESS [16.978s]
[INFO] ManifoldCF - Connectors - ElasticSearch ... SUCCESS [2.101s]
[INFO] ManifoldCF - Test materials ... SUCCESS [0.020s]
[INFO] ManifoldCF - Test Materials - Alfresco WAR FAILURE [4.305s]
[INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
[INFO] ManifoldCF - Tests SKIPPED
[INFO] ManifoldCF - Test - ElasticSearch . SKIPPED
[INFO] ManifoldCF - Test - Alfresco .. SKIPPED
[INFO] ManifoldCF - Test - Wiki .. SKIPPED
[INFO] ManifoldCF - Test - CMIS .. SKIPPED
[INFO] ManifoldCF - Test - Filesystem SKIPPED
[INFO] ManifoldCF - Test - Sharepoint SKIPPED
[INFO] ManifoldCF - Test - RSS ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2:54.944s
[INFO] Finished at: Tue Sep 04 03:10:14 EEST 2012
[INFO] Final Memory: 24M/81M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack-dependencies
(unpack-amps
[jira] [Updated] (CONNECTORS-525) Upgrade to OpenCMIS 0.7.0
[ https://issues.apache.org/jira/browse/CONNECTORS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi updated CONNECTORS-525: -- Fix Version/s: ManifoldCF 0.7 Upgrade to OpenCMIS 0.7.0 - Key: CONNECTORS-525 URL: https://issues.apache.org/jira/browse/CONNECTORS-525 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.7 Original Estimate: 2h Remaining Estimate: 2h We should upgrade CMIS Connector with the latest version of the OpenCMIS library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13447819#comment-13447819
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
Ok, my Mac is crashed and then I retried and the selected version is 4.0 (2010).
Now it returns a different exception, maybe a little step forward:
Service interruption reported for job 1346775681055 connection 'SharePoint
2010': Remote procedure exception: List
'{715A7457-3366-40C0-80F4-FC9BCAE8CEC8}' does not exist at site with URL
'http://win-0hb0c25kl3n/my/personal/administrator'.
It seems that there is an issue about the site url for the list or something
similar. The site URL for the list should be the following:
http://win-0hb0c25kl3n/my/personal/administrator/demosite
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Where do you MCF committers live?
Hi Erlend, I live in Rome (Italy) but sometimes I travel around Europe. For example in November I will be in Berlin for the Alfresco DevCon 2012. I will keep a class during the first day for the Advanced Training. We could stay in touch on this list aboud our trips or anyway on LinkedIn I update trips on my profile ;) Cheers, Piergiorgio Il giorno 15/ago/2012 10:55, Erlend Garåsen e.f.gara...@usit.uio.no ha scritto: Since I'm traveling a lot, I'm curious about where you committers live in the world. I have already met Karl in Boston in May this year, and I would like to meet other committers as well. I live in Oslo, Norway's capital and largest city. Erlend -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
[jira] [Commented] (CONNECTORS-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431660#comment-13431660
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
Ok I installed Apache Ant, Apache SVN and I have built the project directly
from Windows Server.
Then I copied the Microsoft.Sharepoint.dll in the right place in Windows.
Then I executed the setup.bat but it seems that I don't find the right URL to
get the WSDL, it returns always a code 404.
In the README is mentioned this URL:
http://your server name:server port/server
location/_vti_bin/MCPermissions.asmx
But now on my SharePoint instance I have this URLs:
Administration:
http://win-0hb0c25kl3n:33445/default.aspx
My personal documents on my site:
http://win-0hb0c25kl3n/my/personal/administrator/default.aspx
Have you got some ideas about what could be the right URL to get WSDL?
Any feedback is welcome :)
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https
[jira] [Commented] (CONNECTORS-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427315#comment-13427315
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
Finally I have finished a complete SharePoint installation in my virtual
machine based on Windows Server 2008 R2, SQL Server 2008 R2 and SharePoint 2010
SP1 :-P
The next steps are:
- configuring a personal site with some documents in the document library
- download, compile and run ManifoldCF on this environment
- execute tests against SharePoint
I'll let you know soon any updates on this.
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release ManifoldCF SharePoint 2007 Plugin 0.2, RC0
Hi, I checked the signatures for the packages and I taken a look at the code. +1 from me. Cheers, Piergiorgio 2012/7/17 Karl Wright daddy...@gmail.com Please vote on whether to release the Apache ManifoldCF SharePoint 2007 Plugin 0.2, RC0. The release artifact can be found at: http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2007-plugin-0.2 There's also an svn tag at: https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2007/tags/release-0.2-RC0 As posted earlier, the release has no source code changes, just better instructions, a new name, and now includes the Permissions.wsdl file. Thanks! Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Commented] (CONNECTORS-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418126#comment-13418126
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
I'm downloading Windows Server 2008 R2 and SharePoint 2010, and during the next
week I'll try to take a look at this issue.
In this way I can start to use my MSDN account :D
I'll let you know more soon...
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
