Re: Upgrade ManifoldCF to JDK 1.6
Ok, I should try today! I'll let you know. Thank you. Piergiorgio Il giorno 19 aprile 2012 04:27, Karl Wright daddy...@gmail.com ha scritto: I've committed the changes to upgrade ManifoldCF to require JDK 1.6. I've also made sure that the Maven build is consistent with the ant build in this regard. Please let me know if you run into any problems. Karl -- Piergiorgio Lucidi http://www.open4dev.com
Re: Upgrade ManifoldCF to JDK 1.6
For what it is worth, there were a number of things broken in the maven build for the 0.5-incubating version we just shipped. Karl On Thu, Apr 19, 2012 at 2:33 AM, Piergiorgio Lucidi piergior...@apache.org wrote: Ok, I should try today! I'll let you know. Thank you. Piergiorgio Il giorno 19 aprile 2012 04:27, Karl Wright daddy...@gmail.com ha scritto: I've committed the changes to upgrade ManifoldCF to require JDK 1.6. I've also made sure that the Maven build is consistent with the ant build in this regard. Please let me know if you run into any problems. Karl -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Commented] (CONNECTORS-193) Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods
[ https://issues.apache.org/jira/browse/CONNECTORS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257515#comment-13257515 ] Erlend Garåsen commented on CONNECTORS-193: --- Such as the JavaScript method SelectTab? This is not only related to the GTS and Solr connector, but all of them. At least the connectors I have checked. Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods - Key: CONNECTORS-193 URL: https://issues.apache.org/jira/browse/CONNECTORS-193 Project: ManifoldCF Issue Type: Task Components: GTS connector, Lucene/SOLR connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Erlend Garåsen Fix For: ManifoldCF next The convention for form elements and javascript methods is that all element names and methods must begin with lowercase oc. The convention for output specification tabs is that the tab name should contain the name of the target, e.g. GTS Parameters or Solr Metadata Mapping. -- 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
[jira] [Commented] (CONNECTORS-193) Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods
[ https://issues.apache.org/jira/browse/CONNECTORS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257519#comment-13257519 ] Karl Wright commented on CONNECTORS-193: No, the SelectTab JS method is provided by the framework. I am talking about Javascript methods that are local to specific output connectors. Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods - Key: CONNECTORS-193 URL: https://issues.apache.org/jira/browse/CONNECTORS-193 Project: ManifoldCF Issue Type: Task Components: GTS connector, Lucene/SOLR connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Erlend Garåsen Fix For: ManifoldCF next The convention for form elements and javascript methods is that all element names and methods must begin with lowercase oc. The convention for output specification tabs is that the tab name should contain the name of the target, e.g. GTS Parameters or Solr Metadata Mapping. -- 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
[jira] [Created] (CONNECTORS-462) Change and characters to HTML entities in connectors
Change and characters to HTML entities in connectors Key: CONNECTORS-462 URL: https://issues.apache.org/jira/browse/CONNECTORS-462 Project: ManifoldCF Issue Type: Bug Components: Alfresco connector, CMIS connector, Documentum connector, Elastic Search connector, eRoom connector, File system connector, FileNet connector, GTS connector, JCIFS connector, JDBC connector, LiveLink connector, Lucene/SOLR connector, Memex connector, Meridio connector, OpenSearchServer connector, RSS connector, SharePoint connector, Web connector, Wiki connector Affects Versions: ManifoldCF 0.5, ManifoldCF 0.4, ManifoldCF 0.3, ManifoldCF 0.2, ManifoldCF 0.1 Reporter: Erlend Garåsen Assignee: Erlend Garåsen Fix For: ManifoldCF 0.6 There are some characters in several connectors which should be changed to HTML entities instead, especially related to certificate outputs: {code} nobr+org.apache.manifoldcf.ui.util.Encoder.bodyEscape(param)+=+Integer.toString(kmanager.getContents().length)+ certificate(s)/nobrbr/ {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
[jira] [Commented] (CONNECTORS-347) MySQL HopCount test sometimes fails
[ https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257899#comment-13257899 ] Karl Wright commented on CONNECTORS-347: Just saw it again; clearly it is real. MySQL HopCount test sometimes fails --- Key: CONNECTORS-347 URL: https://issues.apache.org/jira/browse/CONNECTORS-347 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next The HopcountMySQLIT test sometimes fails complaining that it is expecting to see 6 documents but only sees 4. {code} [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong number of documents processed - expected 6, saw 4 [junit] at org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152) {code} This does not happen on every run. -- 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
[jira] [Issue Comment Edited] (CONNECTORS-347) MySQL HopCount test sometimes fails
[ https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257899#comment-13257899 ] Karl Wright edited comment on CONNECTORS-347 at 4/19/12 11:23 PM: -- Just saw it again; clearly it is real. My working hypothesis is that the counts returned by count(x) in the SQL statements are in fact not synchronized with the transactions, so maybe the count can run behind. The context in which this happens is an initial crawl of six documents, with a hopcount filter. If the filter is not working the count would be 7; with a working filter, it's 6. But how can we then get 4? was (Author: kwri...@metacarta.com): Just saw it again; clearly it is real. MySQL HopCount test sometimes fails --- Key: CONNECTORS-347 URL: https://issues.apache.org/jira/browse/CONNECTORS-347 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next The HopcountMySQLIT test sometimes fails complaining that it is expecting to see 6 documents but only sees 4. {code} [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong number of documents processed - expected 6, saw 4 [junit] at org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152) {code} This does not happen on every run. -- 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
[jira] [Updated] (CONNECTORS-347) MySQL HopCount test sometimes fails
[ https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-347: --- Affects Version/s: ManifoldCF 0.6 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.6 MySQL HopCount test sometimes fails --- Key: CONNECTORS-347 URL: https://issues.apache.org/jira/browse/CONNECTORS-347 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The HopcountMySQLIT test sometimes fails complaining that it is expecting to see 6 documents but only sees 4. {code} [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong number of documents processed - expected 6, saw 4 [junit] at org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152) {code} This does not happen on every run. -- 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
[jira] [Issue Comment Edited] (CONNECTORS-347) MySQL HopCount test sometimes fails
[ https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257899#comment-13257899 ] Karl Wright edited comment on CONNECTORS-347 at 4/20/12 1:42 AM: - Just saw it again; clearly it is real. My working hypothesis is that the counts returned by count() in the SQL statements are in fact not synchronized with the transactions, so maybe the count can run behind. The context in which this happens is an initial crawl of six documents, with a hopcount filter. If the filter is not working the count would be 7; with a working filter, it's 6. But how can we then get 4? was (Author: kwri...@metacarta.com): Just saw it again; clearly it is real. My working hypothesis is that the counts returned by count(x) in the SQL statements are in fact not synchronized with the transactions, so maybe the count can run behind. The context in which this happens is an initial crawl of six documents, with a hopcount filter. If the filter is not working the count would be 7; with a working filter, it's 6. But how can we then get 4? MySQL HopCount test sometimes fails --- Key: CONNECTORS-347 URL: https://issues.apache.org/jira/browse/CONNECTORS-347 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The HopcountMySQLIT test sometimes fails complaining that it is expecting to see 6 documents but only sees 4. {code} [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong number of documents processed - expected 6, saw 4 [junit] at org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152) {code} This does not happen on every run. -- 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