[jira] [Updated] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Keller updated CONNECTORS-240: --- Attachment: oss-mfc-site.patch I have tried to update the documentation to include references to OpenSearchServer each time the documentation is about output connectors. I added a new paragraph in the end-user documentation. At the moment it is minimalistic, I will now work on this paragraph adding more details including screen capture. > OpenSearchServer connector needs end-user documentation > --- > > Key: CONNECTORS-240 > URL: https://issues.apache.org/jira/browse/CONNECTORS-240 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright > Attachments: oss-mfc-site.patch > > > We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-248) File system crawl with HSQLDB aborts with a constraint error
[ https://issues.apache.org/jira/browse/CONNECTORS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095067#comment-13095067 ] Karl Wright commented on CONNECTORS-248: The constraint being violated appears to be the primary key for the table, which is the "id" column. This is very strange because the update operation in question is not changing the "id" column in any way, but rather another column. The update uses the clause ... WHERE id IN (...) to apply the update to multiple rows at a single time. So I can't think of any reason this can possibly result in a unique constraint violation. This is the second bizarre bug I've seen when crawling with HSQLDB. I'm beginning to think that there's a funky sort of race condition in this database. Either that, or we're seeing a misleading error message, which really means something else (maybe that two transactions are trying to write the same record or something). I think I'm going to have to escalate this to the HSQLDB group. > File system crawl with HSQLDB aborts with a constraint error > > > Key: CONNECTORS-248 > URL: https://issues.apache.org/jira/browse/CONNECTORS-248 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process, Framework core >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright > > While running two jobs with overlapping files with HSQLDB, I got this error > on the second job that aborted it: > Error: integrity constraint violation: unique constraint or index violation; > SYS_PK_10041 table: INGESTSTATUS > The complete exception is here: > ERROR 2011-08-31 21:07:06,029 (Worker thread '34') - Exception tossed: > integrity constraint violation: unique constraint or index violation; > SYS_PK_10041 table: INGESTSTATUS > org.apache.manifoldcf.core.interfaces.ManifoldCFException: integrity > constraint violation: unique constraint or index violation; SYS_PK_10041 > table: INGESTSTATUS > at > org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.reinterpretException(DBInterfaceHSQLDB.java:587) > at > org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:607) > at > org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performUpdate(DBInterfaceHSQLDB.java:242) > at > org.apache.manifoldcf.core.database.BaseTable.performUpdate(BaseTable.java:88) > at > org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.updateRowIds(IncrementalIngester.java:628) > at > org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentCheckMultiple(IncrementalIngester.java:588) > at > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:653) > Caused by: java.sql.SQLException: integrity constraint violation: unique > constraint or index violation; SYS_PK_10041 table: INGESTSTATUS > at org.hsqldb.jdbc.Util.sqlException(Util.java:255) > at > org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4659) > at > org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(JDBCPreparedStatement.java:311) > at > org.apache.manifoldcf.core.database.Database.execute(Database.java:606) > at > org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421) > Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique > constraint or index violation; SYS_PK_10041 table: INGESTSTATUS > at org.hsqldb.error.Error.error(Error.java:134) > at org.hsqldb.Constraint.getException(Constraint.java:914) > at org.hsqldb.index.IndexAVL.insert(IndexAVL.java:731) > at org.hsqldb.persist.RowStoreAVL.indexRow(RowStoreAVL.java:171) > at org.hsqldb.persist.RowStoreAVLDisk.indexRow(RowStoreAVLDisk.java:169) > at > org.hsqldb.TransactionManagerMVCC.addInsertAction(TransactionManagerMVCC.java:401) > at org.hsqldb.Session.addInsertAction(Session.java:434) > at org.hsqldb.Table.insertSingleRow(Table.java:2553) > at org.hsqldb.StatementDML.update(StatementDML.java:1032) > at org.hsqldb.StatementDML.executeUpdateStatement(StatementDML.java:541) > at org.hsqldb.StatementDML.getResult(StatementDML.java:196) > at org.hsqldb.StatementDMQL.execute(StatementDMQL.java:190) > at org.hsqldb.Session.executeCompiledStatement(Session.java:1340) > at org.hsqldb.Session.execute(Session.java:993) > at > org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4651) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-248) File system crawl with HSQLDB aborts with a constraint error
File system crawl with HSQLDB aborts with a constraint error Key: CONNECTORS-248 URL: https://issues.apache.org/jira/browse/CONNECTORS-248 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright While running two jobs with overlapping files with HSQLDB, I got this error on the second job that aborted it: Error: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS The complete exception is here: ERROR 2011-08-31 21:07:06,029 (Worker thread '34') - Exception tossed: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS org.apache.manifoldcf.core.interfaces.ManifoldCFException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.reinterpretException(DBInterfaceHSQLDB.java:587) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:607) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performUpdate(DBInterfaceHSQLDB.java:242) at org.apache.manifoldcf.core.database.BaseTable.performUpdate(BaseTable.java:88) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.updateRowIds(IncrementalIngester.java:628) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentCheckMultiple(IncrementalIngester.java:588) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:653) Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4659) at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(JDBCPreparedStatement.java:311) at org.apache.manifoldcf.core.database.Database.execute(Database.java:606) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421) Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.error.Error.error(Error.java:134) at org.hsqldb.Constraint.getException(Constraint.java:914) at org.hsqldb.index.IndexAVL.insert(IndexAVL.java:731) at org.hsqldb.persist.RowStoreAVL.indexRow(RowStoreAVL.java:171) at org.hsqldb.persist.RowStoreAVLDisk.indexRow(RowStoreAVLDisk.java:169) at org.hsqldb.TransactionManagerMVCC.addInsertAction(TransactionManagerMVCC.java:401) at org.hsqldb.Session.addInsertAction(Session.java:434) at org.hsqldb.Table.insertSingleRow(Table.java:2553) at org.hsqldb.StatementDML.update(StatementDML.java:1032) at org.hsqldb.StatementDML.executeUpdateStatement(StatementDML.java:541) at org.hsqldb.StatementDML.getResult(StatementDML.java:196) at org.hsqldb.StatementDMQL.execute(StatementDMQL.java:190) at org.hsqldb.Session.executeCompiledStatement(Session.java:1340) at org.hsqldb.Session.execute(Session.java:993) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4651) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-247) Need a set of tests for the scripting language client
Need a set of tests for the scripting language client - Key: CONNECTORS-247 URL: https://issues.apache.org/jira/browse/CONNECTORS-247 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor We need unit tests for the script language client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-58) ManifoldCF scripting language, executed via the API, plus "example" jobs for file system and web crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-58. --- Resolution: Fixed Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright Decided only to include file system crawl script, since it demonstrates pretty near everything important. r1163882 for the last of many commits for this feature. > ManifoldCF scripting language, executed via the API, plus "example" jobs for > file system and web crawl > --- > > Key: CONNECTORS-58 > URL: https://issues.apache.org/jira/browse/CONNECTORS-58 > Project: ManifoldCF > Issue Type: Sub-task > Components: Examples, Scripting client >Reporter: Jack Krupansky >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.3 > > > Creating a basic connection setup to do a relatively simple crawl for a file > system or web can be a daunting task for someone new to LCF. So, it would be > nice to have a scripting file that supports an abbreviated API (subset of the > full API discussed in CONNECTORS-56) sufficient to create a default set of > connections and example jobs that the new user can choose from. > Beyond this initial need, this script format might be a useful form to "dump" > all of the connections and jobs in the LCF database in a form that can be > used to recreate an LCF configuration. Kind of a "dump and reload" > capability. That in fact might be how the initial example script gets created. > Those are two distinct use cases, but could utilize the same feature. > The example script could have example jobs to crawl a subdirectory of LCF, > crawl the LCF wiki, etc. > There could be more than one script. There might be example scripts for each > form of connector. > This capability should be available for both QuickStart and the general > release of LCF. > As just one possibility, the script format might be a sequence of JSON > expressions, each with an initial string analogous to a servlet path to > specify the operation to be performed, followed by the JSON form of the > connection or job or other LCF object. Or, some other format might be more > suitable. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-246) A file crawl exited with an "unexpected jobqueue status" error under HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095023#comment-13095023 ] Karl Wright commented on CONNECTORS-246: It occurs to me that this might have happened as a result of a cross-job bug. I may have been deleting one job while running another that had shared documents. I'll experiment a bit and see if I can make it happen again. > A file crawl exited with an "unexpected jobqueue status" error under HSQLDB > --- > > Key: CONNECTORS-246 > URL: https://issues.apache.org/jira/browse/CONNECTORS-246 > Project: ManifoldCF > Issue Type: Bug >Reporter: Karl Wright >Assignee: Karl Wright > > Under HSQLDB, a file crawl terminated with: Error: Unexpected jobqueue status > - record id 1314721269570, expecting active status. > The full trace was: > ERROR 2011-08-30 12:23:48,962 (Worker thread '38') - Exception tossed: > Unexpected jobqueue status - record id 1314721269570, expecting active status > org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected > jobqueue status - record id 1314721269570, expecting active status > at > org.apache.manifoldcf.crawler.jobs.JobQueue.updateCompletedRecord(JobQueue.java:633) > at > org.apache.manifoldcf.crawler.jobs.JobManager.markDocumentCompletedMultiple(JobManager.java:2386) > at > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:798) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-245) Creating a job through the API with no schedule creates an incorrect schedule entry
[ https://issues.apache.org/jira/browse/CONNECTORS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-245. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1163744. > Creating a job through the API with no schedule creates an incorrect schedule > entry > --- > > Key: CONNECTORS-245 > URL: https://issues.apache.org/jira/browse/CONNECTORS-245 > Project: ManifoldCF > Issue Type: Bug > Components: API >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.3 > > > When I dump a job using the API that has no schedule, and create another one > using the same dumped JSON parameters, I get: > Scheduled time: Any day of week at midnight in January on the 1st of > the month > This is obviously incorrect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-246) A file crawl exited with an "unexpected jobqueue status" error under HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094456#comment-13094456 ] Karl Wright commented on CONNECTORS-246: r1163591 for some additional debugging info should this happen again. > A file crawl exited with an "unexpected jobqueue status" error under HSQLDB > --- > > Key: CONNECTORS-246 > URL: https://issues.apache.org/jira/browse/CONNECTORS-246 > Project: ManifoldCF > Issue Type: Bug >Reporter: Karl Wright >Assignee: Karl Wright > > Under HSQLDB, a file crawl terminated with: Error: Unexpected jobqueue status > - record id 1314721269570, expecting active status. > The full trace was: > ERROR 2011-08-30 12:23:48,962 (Worker thread '38') - Exception tossed: > Unexpected jobqueue status - record id 1314721269570, expecting active status > org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected > jobqueue status - record id 1314721269570, expecting active status > at > org.apache.manifoldcf.crawler.jobs.JobQueue.updateCompletedRecord(JobQueue.java:633) > at > org.apache.manifoldcf.crawler.jobs.JobManager.markDocumentCompletedMultiple(JobManager.java:2386) > at > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:798) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Problems during committing
Hi Tommaso, ok the problem is solved now :) Thank you very much for your support! Piergiorgio 2011/8/31 Tommaso Teofili > Hi PJ, > your problems should be fixed now. > Cheers, > Tommaso > > 2011/8/30 Piergiorgio Lucidi > > > Infrastructure said me that I don't have permissions to commit on > Manifold > > because my account now is associated only to incubator. > > > > I forwarded to Tommaso the problem and he confirmed that last week the > > committership procedure has changed. > > That's why now I can't execute a commit, my account needs to be > associated > > to lucene-connectors group. > > > > Tommaso should solve this problem soon. > > > > Thank you all for the support. > > Piergiorgio > > > > 2011/8/30 Karl Wright > > > > > If they don't get back to you soon, I'd ask Tommaso to talk to his > > > infrastructure contact to see if they can figure out what's wrong. > > > > > > Karl > > > > > > > > > On Tue, Aug 30, 2011 at 3:13 AM, Piergiorgio Lucidi > > > wrote: > > > > I created an issue on Infrastructure in Jira. > > > > I hope that they help me quickly. > > > > > > > > Thank you. > > > > Piergiorgio > > > > > > > > 2011/8/30 Karl Wright > > > > > > > >> Still works for me. > > > >> If you can't figure out what changed, you might want to file an > INFRA > > > >> ticket in Jira. > > > >> > > > >> Karl > > > >> > > > >> > > > >> On Mon, Aug 29, 2011 at 1:54 PM, Karl Wright > > > wrote: > > > >> > I haven't had trouble, but the last time I tried a commit was at > > 9:00 > > > >> > AM EDT this morning. > > > >> > Karl > > > >> > > > > >> > On Mon, Aug 29, 2011 at 12:18 PM, Piergiorgio Lucidi > > > >> > wrote: > > > >> >> Hi guys, > > > >> >> > > > >> >> I can't commit anymore on the project, do you have the same > > problem? > > > >> >> > > > >> >> The SVN server returns to me the following message for any file > > that > > > I'm > > > >> >> trying to commit: > > > >> >> > > > >> >> svn: Commit failed (details follow): > > > >> >>> svn: CHECKOUT of > > > >> >>> > > > >> > > > > > > '/repos/asf/!svn/ver/1056132/incubator/lcf/trunk/site/src/documentation/content/xdocs/end-user-documentation.xml': > > > >> >>> 403 Forbidden (https://svn.apache.org) > > > >> >> > > > >> >> > > > >> >> I tried to directly access to > > > >> >> > > > >> > > > > > > https://svn.apache.org/repos/asf/!svn/ver/1056132/incubator/lcf/trunk/site/src/documentation/content/xdocs/end-user-documentation.xmland > > > >> >> this file from the browser could be read correctly. > > > >> >> > > > >> >> Could be a problem of the Apache server certificate that now is > not > > > >> valid? > > > >> >> > > > >> >> Thank you any suggestions. > > > >> >> Piergiorgio > > > >> >> > > > >> >> -- > > > >> >> Piergiorgio Lucidi > > > >> >> http://about.me/piergiorgiolucidi > > > >> >> > > > >> > > > > >> > > > > > > > > > > > > > > > > -- > > > > Piergiorgio Lucidi > > > > http://about.me/piergiorgiolucidi > > > > > > > > > > > > > > > -- > > Piergiorgio Lucidi > > http://about.me/piergiorgiolucidi > > > -- Piergiorgio Lucidi http://about.me/piergiorgiolucidi
[jira] [Resolved] (CONNECTORS-229) CMIS connector needs to be documented in "how to build and deploy"
[ https://issues.apache.org/jira/browse/CONNECTORS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-229. --- Resolution: Fixed r1163569 > CMIS connector needs to be documented in "how to build and deploy" > -- > > Key: CONNECTORS-229 > URL: https://issues.apache.org/jira/browse/CONNECTORS-229 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Piergiorgio Lucidi > Original Estimate: 4h > Remaining Estimate: 4h > > The following pages needs to be updated to include the CMIS connector: > * how-to-build-and-deploy > * end-user-documentation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-229) CMIS connector needs to be documented in "how to build and deploy"
[ https://issues.apache.org/jira/browse/CONNECTORS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi updated CONNECTORS-229: -- Comment: was deleted (was: r1163569) > CMIS connector needs to be documented in "how to build and deploy" > -- > > Key: CONNECTORS-229 > URL: https://issues.apache.org/jira/browse/CONNECTORS-229 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Piergiorgio Lucidi > Original Estimate: 4h > Remaining Estimate: 4h > > The following pages needs to be updated to include the CMIS connector: > * how-to-build-and-deploy > * end-user-documentation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-229) CMIS connector needs to be documented in "how to build and deploy"
[ https://issues.apache.org/jira/browse/CONNECTORS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094421#comment-13094421 ] Piergiorgio Lucidi commented on CONNECTORS-229: --- r1163569 > CMIS connector needs to be documented in "how to build and deploy" > -- > > Key: CONNECTORS-229 > URL: https://issues.apache.org/jira/browse/CONNECTORS-229 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Piergiorgio Lucidi > Original Estimate: 4h > Remaining Estimate: 4h > > The following pages needs to be updated to include the CMIS connector: > * how-to-build-and-deploy > * end-user-documentation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Problems during committing
Hi PJ, your problems should be fixed now. Cheers, Tommaso 2011/8/30 Piergiorgio Lucidi > Infrastructure said me that I don't have permissions to commit on Manifold > because my account now is associated only to incubator. > > I forwarded to Tommaso the problem and he confirmed that last week the > committership procedure has changed. > That's why now I can't execute a commit, my account needs to be associated > to lucene-connectors group. > > Tommaso should solve this problem soon. > > Thank you all for the support. > Piergiorgio > > 2011/8/30 Karl Wright > > > If they don't get back to you soon, I'd ask Tommaso to talk to his > > infrastructure contact to see if they can figure out what's wrong. > > > > Karl > > > > > > On Tue, Aug 30, 2011 at 3:13 AM, Piergiorgio Lucidi > > wrote: > > > I created an issue on Infrastructure in Jira. > > > I hope that they help me quickly. > > > > > > Thank you. > > > Piergiorgio > > > > > > 2011/8/30 Karl Wright > > > > > >> Still works for me. > > >> If you can't figure out what changed, you might want to file an INFRA > > >> ticket in Jira. > > >> > > >> Karl > > >> > > >> > > >> On Mon, Aug 29, 2011 at 1:54 PM, Karl Wright > > wrote: > > >> > I haven't had trouble, but the last time I tried a commit was at > 9:00 > > >> > AM EDT this morning. > > >> > Karl > > >> > > > >> > On Mon, Aug 29, 2011 at 12:18 PM, Piergiorgio Lucidi > > >> > wrote: > > >> >> Hi guys, > > >> >> > > >> >> I can't commit anymore on the project, do you have the same > problem? > > >> >> > > >> >> The SVN server returns to me the following message for any file > that > > I'm > > >> >> trying to commit: > > >> >> > > >> >> svn: Commit failed (details follow): > > >> >>> svn: CHECKOUT of > > >> >>> > > >> > > > '/repos/asf/!svn/ver/1056132/incubator/lcf/trunk/site/src/documentation/content/xdocs/end-user-documentation.xml': > > >> >>> 403 Forbidden (https://svn.apache.org) > > >> >> > > >> >> > > >> >> I tried to directly access to > > >> >> > > >> > > > https://svn.apache.org/repos/asf/!svn/ver/1056132/incubator/lcf/trunk/site/src/documentation/content/xdocs/end-user-documentation.xmland > > >> >> this file from the browser could be read correctly. > > >> >> > > >> >> Could be a problem of the Apache server certificate that now is not > > >> valid? > > >> >> > > >> >> Thank you any suggestions. > > >> >> Piergiorgio > > >> >> > > >> >> -- > > >> >> Piergiorgio Lucidi > > >> >> http://about.me/piergiorgiolucidi > > >> >> > > >> > > > >> > > > > > > > > > > > > -- > > > Piergiorgio Lucidi > > > http://about.me/piergiorgiolucidi > > > > > > > > > -- > Piergiorgio Lucidi > http://about.me/piergiorgiolucidi >
