[jira] [Resolved] (CONNECTORS-459) Move to JDK1.6
[ https://issues.apache.org/jira/browse/CONNECTORS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-459. Resolution: Fixed Move to JDK1.6 -- Key: CONNECTORS-459 URL: https://issues.apache.org/jira/browse/CONNECTORS-459 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 It turns out that there are a number of dependency upgrades we can't do until we move completely to jdk1.6, such as going to jetty 7, tomcat 7 components, axis 2.x, etc. In addition, certain connectors already require jdk1.6 (the alfresco connector, for instance). Other dependencies must be built by us in order to get a jdk1.5-compatible version. Since jdk1.6 has been end-of-life'd, it may be the time to make this move. -- 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] [Resolved] (CONNECTORS-458) Incubator site has moved; adjust crawler-ui documentation reference accordingly
[ https://issues.apache.org/jira/browse/CONNECTORS-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-458. Resolution: Not A Problem Incubator site has moved; adjust crawler-ui documentation reference accordingly --- Key: CONNECTORS-458 URL: https://issues.apache.org/jira/browse/CONNECTORS-458 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Fix For: ManifoldCF 0.6 The ManifoldCF site has moved from http://incubator.apache.org/connectors to http://incubator.apache.org/content/connectors. The crawler UI references the on-line documentation and should be updated. -- 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] [Resolved] (CONNECTORS-438) Only the current release should be referred to by the documentation on the mirror - the rest should point to the archive
[ https://issues.apache.org/jira/browse/CONNECTORS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-438. Resolution: Fixed Resolved as part of another commit Only the current release should be referred to by the documentation on the mirror - the rest should point to the archive Key: CONNECTORS-438 URL: https://issues.apache.org/jira/browse/CONNECTORS-438 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The download page should refer to only the current release via the mirror. All older releases should refer to http://archive.apache.org/dist. -- 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] [Resolved] (CONNECTORS-456) README.txt for binary distribution refers to dist directory incorrectly
[ https://issues.apache.org/jira/browse/CONNECTORS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-456. Resolution: Fixed README.txt for binary distribution refers to dist directory incorrectly --- Key: CONNECTORS-456 URL: https://issues.apache.org/jira/browse/CONNECTORS-456 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.6 The README.txt for binary distribution refers to dist/example directory instead of just example. -- 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] [Resolved] (CONNECTORS-439) How-to-build-and-deploy documentation needs to describe how to use download-dependencies ant target
[ https://issues.apache.org/jira/browse/CONNECTORS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-439. Resolution: Fixed Was resolved by r1309020, committed for another ticket. How-to-build-and-deploy documentation needs to describe how to use download-dependencies ant target --- Key: CONNECTORS-439 URL: https://issues.apache.org/jira/browse/CONNECTORS-439 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 Since the download of binary dependencies is no longer optional, how-to-build-and-deploy documentation needs to describe how to use download-dependencies ant target. -- 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] [Resolved] (CONNECTORS-457) Strange i18n behavior on some Italian or German machines
[ https://issues.apache.org/jira/browse/CONNECTORS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-457. Resolution: Fixed I am told by Alex Ott that the problem is fixed. Strange i18n behavior on some Italian or German machines Key: CONNECTORS-457 URL: https://issues.apache.org/jira/browse/CONNECTORS-457 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.5 When ManifoldCF is run on some machines that are neither en_US or ja_JP, certain specific messages render with the key value rather than falling back to en_US. One specific field that this happens to is in listconnections.jsp, and is the listconnections.ListOfRepositoryConnections message. -- 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] [Resolved] (CONNECTORS-450) Execs in ant build do not properly check for errors
[ https://issues.apache.org/jira/browse/CONNECTORS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-450. Resolution: Fixed Execs in ant build do not properly check for errors --- Key: CONNECTORS-450 URL: https://issues.apache.org/jira/browse/CONNECTORS-450 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The exec ant calls are not checking for errors; this can cause builds to fail later if (for instance) the svn client is at the wrong version. -- 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] [Resolved] (CONNECTORS-451) mvn-bootstrap scripts use incorrect target for ant
[ https://issues.apache.org/jira/browse/CONNECTORS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-451. Resolution: Fixed mvn-bootstrap scripts use incorrect target for ant -- Key: CONNECTORS-451 URL: https://issues.apache.org/jira/browse/CONNECTORS-451 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The mvn-bootstrap scripts don't use the right ant target anymore; they should use ant make-deps not ant download-dependencies. -- 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] [Resolved] (CONNECTORS-452) Postgresql jar not included properly in build
[ https://issues.apache.org/jira/browse/CONNECTORS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-452. Resolution: Fixed Assignee: Karl Wright Postgresql jar not included properly in build - Key: CONNECTORS-452 URL: https://issues.apache.org/jira/browse/CONNECTORS-452 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 When you start the ManifoldCF single-process example, you get this: C:\release-0.5\apache-manifoldcf-0.5-incubating-bin\apache-manifoldcf-0.5-incuba ting\examplec:\Program Files\Java\jdk1.5.0_22\bin\java -jar start.jar Configuration file successfully read org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unable to load databa se driver: org.postgresql.Driver at org.apache.manifoldcf.core.database.ConnectionFactory$PoolManager.ens urePoolExists(ConnectionFactory.java:212) at org.apache.manifoldcf.core.database.ConnectionFactory.getConnection(C onnectionFactory.java:55) at org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Dat abase.java:721) at org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.creat e(Database.java:1393) at org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndEx ecute(CacheManager.java:144) at org.apache.manifoldcf.core.database.Database.executeQuery(Database.ja va:185) at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.createUserA ndDatabase(DBInterfacePostgreSQL.java:524) at org.apache.manifoldcf.core.system.ManifoldCF.createSystemDatabase(Man ifoldCF.java:698) at org.apache.manifoldcf.crawler.system.ManifoldCF.createSystemDatabase( ManifoldCF.java:123) at org.apache.manifoldcf.jettyrunner.ManifoldCFJettyRunner.main(Manifold CFJettyRunner.java:224) Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.apache.manifoldcf.core.database.ConnectionFactory$PoolManager.ens urePoolExists(ConnectionFactory.java:208) ... 9 more -- 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] [Resolved] (CONNECTORS-454) lib and bin distributions should have disclaimer.txt
[ https://issues.apache.org/jira/browse/CONNECTORS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-454. Resolution: Fixed lib and bin distributions should have disclaimer.txt Key: CONNECTORS-454 URL: https://issues.apache.org/jira/browse/CONNECTORS-454 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 Incubator rules say that all packages released under the incubator should have a disclaimer file. -- 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] [Resolved] (CONNECTORS-447) It would be better if the lib distribution contained jars without being under lib
[ https://issues.apache.org/jira/browse/CONNECTORS-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-447. Resolution: Fixed It would be better if the lib distribution contained jars without being under lib --- Key: CONNECTORS-447 URL: https://issues.apache.org/jira/browse/CONNECTORS-447 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Since the lib distribution should contain only what's under lib, we should just ship the contents of lib, without insisting it's in a folder 'lib' too. -- 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] [Resolved] (CONNECTORS-449) UI tests broken due to buggy browser simulator
[ https://issues.apache.org/jira/browse/CONNECTORS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-449. Resolution: Fixed UI tests broken due to buggy browser simulator -- Key: CONNECTORS-449 URL: https://issues.apache.org/jira/browse/CONNECTORS-449 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The UI tests aren't working due to a regression in the browser simulator. -- 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] [Resolved] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process
[ https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-443. Resolution: Fixed All patched jars must be built within ManifoldCF release process Key: CONNECTORS-443 URL: https://issues.apache.org/jira/browse/CONNECTORS-443 Project: ManifoldCF Issue Type: Task Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 Downloading already-built patched jars is not permissible within Apache any longer. The fix to this will entail downloading source and patching that as part of the build process. In order for the build process to succeed on Windows, this currently means that the sources must be checked out using svn. The following changes will therefore need to occur under this ticket: (1) Apache binaries that are available as releases but which are not in Maven should be downloaded and unpacked from http://archive.apache.org/dist. This will include the solr and sharepoint mcf plugins. (2) The download-dependencies target must be split into download-dependencies and download-proprietary-dependencies. The download-dependencies target will become responsible for downloading, patching, and building the non-proprietary packages. Packages that will need to be checked out by this target from svn include: httpclient 3.1, xerces 2.9.1, hsqldb 2.2.8, and jetty 6.1.26. (3) A new release artifact, XXX-dep.zip/tar.gz, will be produced which will contain all the dependency binaries. (4) Any non-sourceable dependency binaries we find must be replaced with a sourced equivalent, or code for it developed from scratch. -- 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] [Resolved] (CONNECTORS-444) README.txt and DEPENDENCIES.txt need to be updated to reflect separation of source and lib distributions
[ https://issues.apache.org/jira/browse/CONNECTORS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-444. Resolution: Fixed README.txt and DEPENDENCIES.txt need to be updated to reflect separation of source and lib distributions Key: CONNECTORS-444 URL: https://issues.apache.org/jira/browse/CONNECTORS-444 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 The README.txt and DEPENDENCIES.txt files need to be updated to mention lib distributions, as well as the new ant targets. While we're at it, the how-to-build-and-deploy page should likewise be updated. -- 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] [Resolved] (CONNECTORS-445) Each artifact must have different license, notice, and readme files
[ https://issues.apache.org/jira/browse/CONNECTORS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-445. Resolution: Fixed Each artifact must have different license, notice, and readme files --- Key: CONNECTORS-445 URL: https://issues.apache.org/jira/browse/CONNECTORS-445 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 Every distribution package that is produced must have a uniquely customized README, LICENSE, and NOTICE file. This means that we can no longer have one set of files at the root level. Instead we will need to create a separate image for each package we create. -- 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] [Resolved] (CONNECTORS-440) Source bin/tar includes solr integration jars and shouldn't
[ https://issues.apache.org/jira/browse/CONNECTORS-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-440. Resolution: Fixed Assignee: Karl Wright Source bin/tar includes solr integration jars and shouldn't --- Key: CONNECTORS-440 URL: https://issues.apache.org/jira/browse/CONNECTORS-440 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 The solr integration jars apparently get included in the source zip/tar. They should be excluded. -- 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] [Resolved] (CONNECTORS-441) Build needs some refactoring on how to handle integration tasks
[ https://issues.apache.org/jira/browse/CONNECTORS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-441. Resolution: Fixed Build needs some refactoring on how to handle integration tasks --- Key: CONNECTORS-441 URL: https://issues.apache.org/jira/browse/CONNECTORS-441 Project: ManifoldCF Issue Type: Task Components: Build Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The integration directories for connectors no longer contain the integration binaries. The binaries are copied twice, once to the integration area, and then to the dist/integration area. A single copy would make life much easier. -- 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] [Resolved] (CONNECTORS-442) Binary distributions should not include build.xml, pom.xml or common-build.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-442. Resolution: Fixed r1308364 Binary distributions should not include build.xml, pom.xml or common-build.xml -- Key: CONNECTORS-442 URL: https://issues.apache.org/jira/browse/CONNECTORS-442 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 Since sources are not included, pom.xml, build.xml, and common-build.xml are useless and confusing in the binary packages. -- 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] [Resolved] (CONNECTORS-437) Remove all binary objects from source distribution
[ https://issues.apache.org/jira/browse/CONNECTORS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-437. Resolution: Fixed Remove all binary objects from source distribution -- Key: CONNECTORS-437 URL: https://issues.apache.org/jira/browse/CONNECTORS-437 Project: ManifoldCF Issue Type: Task Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 A board member of the ASF has indicated that it is a violation of policy for any project to include binary objects as part of its distribution. While the discussion is ongoing, it seems prudent to capture the required modifications to ManifoldCF which will bring it into compliance into a ticket. As far as I see it, these required modifications consist of the following: (1) Separate releases of all dependencies that have been patched. This includes ManifoldCF's patched httpclient, xerces, and jetty dependencies. The patches and/or patched sources are currently in Jira or are in the upstream area of svn. This should also include a Java 1.5 build of HSQLDB, since this database is currently built by its owner only for Java 1.6 and up. ManifoldCF releases of these packages may require modification of the packages' ant builds to also adhere to the new Apache rule. Since we will be checking in sources for non-Apache projects, namely Jetty and HSQLDB, we will need to confirm that this is permitted under Apache rules. If it is not, a separate googlecode project should be created instead to make these artifacts available. (2) Removal of all jars under the lib directory, and under the integration areas of individual connectors. (3) Additional ant download-dependencies actions to download all jars that were formerly in the above locations. (4) Removal of all mention of jars in the LICENSE.txt and NOTICE.txt files. -- 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] [Resolved] (CONNECTORS-436) Main README.txt file is inappropriate for the binary distribution
[ https://issues.apache.org/jira/browse/CONNECTORS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-436. Resolution: Fixed r1305736 Main README.txt file is inappropriate for the binary distribution - Key: CONNECTORS-436 URL: https://issues.apache.org/jira/browse/CONNECTORS-436 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The main README.txt file is inappropriate for the binary distribution in that it seems to indicate you need to build it rather than just run it. -- 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] [Resolved] (CONNECTORS-433) NOTICE copyright date needs updating
[ https://issues.apache.org/jira/browse/CONNECTORS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-433. Resolution: Fixed r1305378 NOTICE copyright date needs updating Key: CONNECTORS-433 URL: https://issues.apache.org/jira/browse/CONNECTORS-433 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 The NOTICE file copyright date does not include 2012. -- 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] [Resolved] (CONNECTORS-434) LICENSE file does not specify which license we are using for dual-licensed jars
[ https://issues.apache.org/jira/browse/CONNECTORS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-434. Resolution: Fixed LICENSE file does not specify which license we are using for dual-licensed jars --- Key: CONNECTORS-434 URL: https://issues.apache.org/jira/browse/CONNECTORS-434 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 The LICENSE file notes some jars which are dual-licensed and does not specify which license we pick. -- 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] [Resolved] (CONNECTORS-432) Quotation marks in translated messages should be removed
[ https://issues.apache.org/jira/browse/CONNECTORS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-432. Resolution: Fixed Assignee: Karl Wright (was: Erlend Garåsen) r1304095 Quotation marks in translated messages should be removed Key: CONNECTORS-432 URL: https://issues.apache.org/jira/browse/CONNECTORS-432 Project: ManifoldCF Issue Type: Task Components: Framework core Affects Versions: ManifoldCF 0.4 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF 0.6 Quotation marks exist in some translated messages, e.g. in common_en_US.properties for the Web Connector. These should be removed and added elsewhere. An example: editjob.ExpirationIntervalMustBeAValidIntegerOrNull=Expiration interval must be a valid integer or null The quotation marks should in the example above be placed in the JSP file instead. -- 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] [Resolved] (CONNECTORS-431) Update all pom.xml files on trunk to specify a version of 0.6
[ https://issues.apache.org/jira/browse/CONNECTORS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-431. Resolution: Fixed Assignee: Karl Wright Update all pom.xml files on trunk to specify a version of 0.6 - Key: CONNECTORS-431 URL: https://issues.apache.org/jira/browse/CONNECTORS-431 Project: ManifoldCF Issue Type: Task Components: Build Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The pom.xml files must all be updated for the new version, 0.6. -- 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] [Resolved] (CONNECTORS-428) Include license label for IPA fonts
[ https://issues.apache.org/jira/browse/CONNECTORS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-428. Resolution: Fixed r1302582 Include license label for IPA fonts --- Key: CONNECTORS-428 URL: https://issues.apache.org/jira/browse/CONNECTORS-428 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.5 The IPA fonts are to be considered Category-B licensed, according to LEGAL-123, so we will need to add mention of them in the licensing materials. See http://www.apache.org/legal/resolved.html#category-b -- 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] [Resolved] (CONNECTORS-429) A job is stopped by SmbException(No process is on the other end of the pipe).
[
https://issues.apache.org/jira/browse/CONNECTORS-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-429.
Resolution: Fixed
Assignee: Karl Wright
r1302762
A job is stopped by SmbException(No process is on the other end of the pipe).
-
Key: CONNECTORS-429
URL: https://issues.apache.org/jira/browse/CONNECTORS-429
Project: ManifoldCF
Issue Type: Bug
Components: JCIFS connector
Affects Versions: ManifoldCF 0.4
Environment: Windows 2003 R2 SE SP2
PostgreSQL8.4
Java 1.6.0_24-b07
Tomcat 6.0.33
ManifoldCF (from trunk | 2012-03-01)
Reporter: takagi
Assignee: Karl Wright
Labels: patch
Fix For: ManifoldCF 0.5
Original Estimate: 1h
Remaining Estimate: 1h
I am using ManifoldCF(from trunk build. 0.5?) for crawling Windows Share
Folder for our application. When I run ManifoldCF sometimes I am getting
SmbException. SmbException occur more often around crawling 70,000 files
over. I try to reduce this JCIFS connection(2-5). However, SmbException will
occur.
I read ManifoldCF Source Code.
SharedDriverConnector.java
+processSMBException()
This method don't handle No process is on the other end of the pipe. I want
to continue the job even in the exception. Therefore, I modified the source
code(SharedDriverConnector.java/Line number 1176). As a result, a job
continue without stopping.
Source Code
http://hb2.sakura.ne.jp/manifoldcf/SharedDriveConnector.java
Source Code Parts
+
else if(se.getMessage().indexOf(No process is on the other end of the
pipe) != -1) {
Logging.connectors.warn(JCIFS: 'No process is on the other end of the
pipe' response when +activity+ for +documentIdentifier+: retrying...,se);
// 'No process is on the other end of the pipe' skip the document and
keep going
throw new ServiceInterruption(Timeout or other service interruption:
+se.getMessage(),se,currentTime + 30L,
currentTime + 3 * 60 * 6L,-1,false);
}
+
--
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] [Resolved] (CONNECTORS-422) Canonical use of Velocity should have one html file per UI tab
[ https://issues.apache.org/jira/browse/CONNECTORS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-422. Resolution: Fixed r1299512 Canonical use of Velocity should have one html file per UI tab -- Key: CONNECTORS-422 URL: https://issues.apache.org/jira/browse/CONNECTORS-422 Project: ManifoldCF Issue Type: Improvement Components: Alfresco connector, CMIS connector, OpenSearchServer connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 Since the 0.5 release is going to be about internationalization and Velocity primarily, we need to spend time now to get the Velocity usage in good example form. Specifically, I think best practice ought to be to have a separate template for each tab. Then the connector code can call all the templates one after another. It makes it easy to add a tab, and easy to maintain. Each template, then, becomes responsible for managing both the tab in its hidden form, as well as the tab in its displayed form. We can do something similar for the view templates. -- 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] [Resolved] (CONNECTORS-381) OpenSearchServer connector needs a UI test
[ https://issues.apache.org/jira/browse/CONNECTORS-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-381. Resolution: Fixed r1298515 OpenSearchServer connector needs a UI test -- Key: CONNECTORS-381 URL: https://issues.apache.org/jira/browse/CONNECTORS-381 Project: ManifoldCF Issue Type: Test Components: OpenSearchServer connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The OpenSearchServer connector needs a UI test, and needs whatever modifications to the UI code are needed to make it testable. -- 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] [Resolved] (CONNECTORS-420) Velocity support should include a model where there is one template for all languages, and tags that you can use for i18n strings
[ https://issues.apache.org/jira/browse/CONNECTORS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-420. Resolution: Fixed r1295926 Velocity support should include a model where there is one template for all languages, and tags that you can use for i18n strings - Key: CONNECTORS-420 URL: https://issues.apache.org/jira/browse/CONNECTORS-420 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The current way we use Velocity templates is to have a different template for each language. That's very wasteful and leads to code duplication. We need to support a way of having one template for all languages. -- 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] [Resolved] (CONNECTORS-415) Minor errors in script engine documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-415. Resolution: Fixed r1293918 Minor errors in script engine documentation --- Key: CONNECTORS-415 URL: https://issues.apache.org/jira/browse/CONNECTORS-415 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 There are a number of places where and are used instead of and . -- 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] [Resolved] (CONNECTORS-416) Can't click any of the buttons on the authentication tab for the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-416. Resolution: Fixed r1293919 Can't click any of the buttons on the authentication tab for the web connector -- Key: CONNECTORS-416 URL: https://issues.apache.org/jira/browse/CONNECTORS-416 Project: ManifoldCF Issue Type: Bug Components: Web connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The session and page authentication buttons do not work. -- 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] [Resolved] (CONNECTORS-413) OpenSearchServer connector hidden tabs use wrong variable variant so escaping is not right
[ https://issues.apache.org/jira/browse/CONNECTORS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-413. Resolution: Fixed Fix Version/s: ManifoldCF 0.5 r1290980 OpenSearchServer connector hidden tabs use wrong variable variant so escaping is not right -- Key: CONNECTORS-413 URL: https://issues.apache.org/jira/browse/CONNECTORS-413 Project: ManifoldCF Issue Type: Bug Reporter: Karl Wright Fix For: ManifoldCF 0.5 The hidden tabs for the OpenSearchServer connector use the _B variant of Velocity variables in some places when they should be using the _A variant. -- 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] [Resolved] (CONNECTORS-410) Rumor has it that the Documentum DFC is now using dfc.properties instead of dmcl.ini
[ https://issues.apache.org/jira/browse/CONNECTORS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-410. Resolution: Fixed Assignee: Karl Wright r1245894 Rumor has it that the Documentum DFC is now using dfc.properties instead of dmcl.ini Key: CONNECTORS-410 URL: https://issues.apache.org/jira/browse/CONNECTORS-410 Project: ManifoldCF Issue Type: Bug Components: Documentum connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Documentum sidecar process scripts make sure that the environment variable DOCUMENTUM is properly set for DFC by looking for dmcl.ini (for Windows) at that location. I've been told that that is no longer valid; we want to look for dfc.properties instead. This is trivial to change once we get confirmation that this is indeed a correct description of the problem, and also whether the DOCUMENTUM environment variable is even necessary any more. -- 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] [Resolved] (CONNECTORS-406) Some ManifoldCF code doesn't use the MultiThreadedHttpConnectionManager
[ https://issues.apache.org/jira/browse/CONNECTORS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-406. Resolution: Fixed Assignee: Karl Wright r1245127 for the OpenSearchServer connector. Some ManifoldCF code doesn't use the MultiThreadedHttpConnectionManager --- Key: CONNECTORS-406 URL: https://issues.apache.org/jira/browse/CONNECTORS-406 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, OpenSearchServer connector, Scripting client Affects Versions: ManifoldCF 0.5 Reporter: Luca Stancapiano Assignee: Karl Wright Fix For: ManifoldCF 0.5 I signal three projects not using the http multithread manager: mcf-opensearch-connector pull-agent (tests) scripting-engine -- 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] [Resolved] (CONNECTORS-407) Ant build does not leave shell scripts with executable bits set for Linux
[ https://issues.apache.org/jira/browse/CONNECTORS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-407. Resolution: Fixed r1243314 Ant build does not leave shell scripts with executable bits set for Linux - Key: CONNECTORS-407 URL: https://issues.apache.org/jira/browse/CONNECTORS-407 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 The ant build does not make the .sh scripts executable, making for a lot of work for Linux users. -- 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] [Resolved] (CONNECTORS-408) Script engine scripts use MCF_HOME inconsistently with other scripts
[ https://issues.apache.org/jira/browse/CONNECTORS-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-408. Resolution: Fixed r1243320 Script engine scripts use MCF_HOME inconsistently with other scripts Key: CONNECTORS-408 URL: https://issues.apache.org/jira/browse/CONNECTORS-408 Project: ManifoldCF Issue Type: Bug Components: Examples Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The script engine scripts do not use MCF_HOME in the same way that other scripts do. The fix is to use a different environment variable for this purpose. -- 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] [Resolved] (CONNECTORS-327) Might be able to save some binary space by only delivering the war files in one place
[ https://issues.apache.org/jira/browse/CONNECTORS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-327. Resolution: Fixed Might be able to save some binary space by only delivering the war files in one place - Key: CONNECTORS-327 URL: https://issues.apache.org/jira/browse/CONNECTORS-327 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 The war files are currently placed in both the multiprocess example and the single process example. We could have them delivered instead to the main dist area, and referenced by the examples using ... In order to make this reasonably configurable, however, we'd also probably want to add properties.xml properties in the single process example that provides paths to the wars explicitly. -- 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] [Resolved] (CONNECTORS-405) Binary distribution is too big
[ https://issues.apache.org/jira/browse/CONNECTORS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-405. Resolution: Fixed r1243050. Binary distribution is too big -- Key: CONNECTORS-405 URL: https://issues.apache.org/jira/browse/CONNECTORS-405 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The binary distribution is some 220MB right now. This is way too big. Options for cutting it down to size include: (1) Remove source code from binary distribution (2) Share common jars across the two examples -- 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] [Resolved] (CONNECTORS-402) Separate the proprietary / non-proprietary deliverables for each connector
[ https://issues.apache.org/jira/browse/CONNECTORS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-402. Resolution: Fixed r1242970 Separate the proprietary / non-proprietary deliverables for each connector -- Key: CONNECTORS-402 URL: https://issues.apache.org/jira/browse/CONNECTORS-402 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Piergiorgio Lucidi Assignee: Karl Wright Fix For: ManifoldCF 0.5 Original Estimate: 24h Remaining Estimate: 24h As we have spoken today this ticket is dedicated to try to work on the build process to separate proprietary and non-proprietary libraries in the release package. In this way, for example, we could have a standard way to release a specific library for the connector (mcf-alfresco-connector) without release proprietary libraries and allow users to add proprietary libraries in a specific folder connector-lib-proprietary that could be added to the ManifoldCF classloader. -- 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] [Resolved] (CONNECTORS-403) Sidecar processes require a different MCF_HOME setting than webapps and agents process
[ https://issues.apache.org/jira/browse/CONNECTORS-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-403. Resolution: Fixed r1242561 Sidecar processes require a different MCF_HOME setting than webapps and agents process -- Key: CONNECTORS-403 URL: https://issues.apache.org/jira/browse/CONNECTORS-403 Project: ManifoldCF Issue Type: Bug Components: Build, Framework crawler agent Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Sidecar processes were moved directly under the dist directory in 0.4-incubating. Unfortunately this means that the sidecar process scripts, which use the environment variable MCF_HOME, require a different MCF_HOME than the main processes and web apps. MCF_HOME is defined by these to be the location of properties.xml. The fix for the ticket is to modify the sidecar process scripts to use the same definition for MCF_HOME. -- 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] [Resolved] (CONNECTORS-400) Make Alfresco's use of Velocity be good enough to be an exemplar for future Velocity development work
[ https://issues.apache.org/jira/browse/CONNECTORS-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-400. Resolution: Fixed r1240934. Make Alfresco's use of Velocity be good enough to be an exemplar for future Velocity development work - Key: CONNECTORS-400 URL: https://issues.apache.org/jira/browse/CONNECTORS-400 Project: ManifoldCF Issue Type: Task Components: Alfresco connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 I'd like to point people at the Alfresco connector as a good example of Velocity use and best practice, so clean up the connector a bit so that that's a good idea. -- 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] [Resolved] (CONNECTORS-398) Alfresco Connector UI Japanese translation would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-398. Resolution: Fixed Alfresco Connector UI Japanese translation would be helpful --- Key: CONNECTORS-398 URL: https://issues.apache.org/jira/browse/CONNECTORS-398 Project: ManifoldCF Issue Type: Improvement Components: Alfresco connector Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-398.patch Original Estimate: 4h Remaining Estimate: 4h A Japanese translation of the Alfresco Connector could be very useful. -- 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] [Resolved] (CONNECTORS-399) Japanese site page does not have 0.4 release information
[ https://issues.apache.org/jira/browse/CONNECTORS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-399. Resolution: Fixed r1240387 Japanese site page does not have 0.4 release information Key: CONNECTORS-399 URL: https://issues.apache.org/jira/browse/CONNECTORS-399 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Trivial Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-399.patch Japanese site needs to be updated to contain release 0.4 information. -- 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] [Resolved] (CONNECTORS-396) CMIS Connector UI Japanese translation
[ https://issues.apache.org/jira/browse/CONNECTORS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-396. Resolution: Fixed r1240389 CMIS Connector UI Japanese translation -- Key: CONNECTORS-396 URL: https://issues.apache.org/jira/browse/CONNECTORS-396 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-396.patch Original Estimate: 1h Remaining Estimate: 1h I updated the Japanese templates with the latest changes and we need to translate some terms in the Japanese language. Maybe Hitoshi could help us here ;) -- 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] [Resolved] (CONNECTORS-387) Japanese fonts are missing from the PDF files generated for the site
[ https://issues.apache.org/jira/browse/CONNECTORS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-387. Resolution: Fixed r1239111 for conditional fonts. Japanese fonts are missing from the PDF files generated for the site Key: CONNECTORS-387 URL: https://issues.apache.org/jira/browse/CONNECTORS-387 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Japanese fonts are missing from the PDFs generated for the site. This page describes how to fix that: http://forrest.apache.org/pluginDocs/plugins_0_90/org.apache.forrest.plugin.output.pdf/ -- 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] [Resolved] (CONNECTORS-393) SharePoint connector does not accept empty username/password
[ https://issues.apache.org/jira/browse/CONNECTORS-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-393. Resolution: Fixed SharePoint connector does not accept empty username/password Key: CONNECTORS-393 URL: https://issues.apache.org/jira/browse/CONNECTORS-393 Project: ManifoldCF Issue Type: Bug Components: SharePoint connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The SharePoint connector does not currently allow an empty username, and thus no authentication. The problem is in the UI Javascript. -- 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] [Resolved] (CONNECTORS-378) Need to modify site to include pointer(s) to ManifoldCF 0.4-incubating and plugins
[ https://issues.apache.org/jira/browse/CONNECTORS-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-378. Resolution: Fixed Need to modify site to include pointer(s) to ManifoldCF 0.4-incubating and plugins -- Key: CONNECTORS-378 URL: https://issues.apache.org/jira/browse/CONNECTORS-378 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The site documentation needs to be updated to include a reference to the latest (0.4-incubating) release. Links to the plugin source distributions are also desirable. -- 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] [Resolved] (CONNECTORS-392) Japanese top page and concepts pages are not fully translated
[ https://issues.apache.org/jira/browse/CONNECTORS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-392. Resolution: Fixed r1235235 Japanese top page and concepts pages are not fully translated - Key: CONNECTORS-392 URL: https://issues.apache.org/jira/browse/CONNECTORS-392 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-392.patch There are some untranslated sentences in Japanese top page and concepts pages. -- 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] [Resolved] (CONNECTORS-384) Ant build scripts are extremely repetitive, and could use clever consolidation
[ https://issues.apache.org/jira/browse/CONNECTORS-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-384. Resolution: Fixed Committed a number of pretty massive reorgs. I didn't move the model entirely to a bottom-driven one, because that would have required invoking the framework targets two dozen times on a complete build. I also did not find a way to share build targets for a list of individual connectors; each connector target needs to have an explicit target of its own in the outer build file. Other than that, though, the reorganization accomplished the goal handsomely. Ant build scripts are extremely repetitive, and could use clever consolidation -- Key: CONNECTORS-384 URL: https://issues.apache.org/jira/browse/CONNECTORS-384 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The ant build scripts don't have any facility for sharing code. Also, it would be good to be able to add new connectors to the build with only local changes to a connector's code, like it is possible to add modules to Lucene/Solr. The same ability ought to apply to integration tests. -- 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] [Resolved] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-385. Resolution: Fixed Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- 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] [Resolved] (CONNECTORS-382) JDBC connector should have Japanese messages
[ https://issues.apache.org/jira/browse/CONNECTORS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-382. Resolution: Fixed r1231751 JDBC connector should have Japanese messages Key: CONNECTORS-382 URL: https://issues.apache.org/jira/browse/CONNECTORS-382 Project: ManifoldCF Issue Type: Improvement Components: JDBC connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-382.patch, CONNECTORS-382.patch JDBC connector's message properties file should have Japanese translations. -- 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] [Resolved] (CONNECTORS-383) JCIF connector should have Japanese messages
[ https://issues.apache.org/jira/browse/CONNECTORS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-383. Resolution: Fixed r1231752 JCIF connector should have Japanese messages Key: CONNECTORS-383 URL: https://issues.apache.org/jira/browse/CONNECTORS-383 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-383.patch Messages in JCIF connector should have Japanese translations. -- 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] [Resolved] (CONNECTORS-379) Merido connector needs to be internationalized
[ https://issues.apache.org/jira/browse/CONNECTORS-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-379. Resolution: Fixed r1230518 Merido connector needs to be internationalized -- Key: CONNECTORS-379 URL: https://issues.apache.org/jira/browse/CONNECTORS-379 Project: ManifoldCF Issue Type: Improvement Components: Meridio connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-379.patch Messages in Merido connector needs to be externalized to properties file. -- 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] [Resolved] (CONNECTORS-376) Meridio connector's Japanese messages are not fully translated
[ https://issues.apache.org/jira/browse/CONNECTORS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-376. Resolution: Fixed Meridio connector's Japanese messages are not fully translated -- Key: CONNECTORS-376 URL: https://issues.apache.org/jira/browse/CONNECTORS-376 Project: ManifoldCF Issue Type: Improvement Components: Meridio connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-376.patch Should translate Meridio connector's Japanese message properties -- 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] [Resolved] (CONNECTORS-339) We need a test for all of the localized versions of the UI
[ https://issues.apache.org/jira/browse/CONNECTORS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-339. Resolution: Fixed We need a test for all of the localized versions of the UI -- Key: CONNECTORS-339 URL: https://issues.apache.org/jira/browse/CONNECTORS-339 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 We need a way of testing the UI for functionality, regressions, and properly formed HTML. -- 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] [Resolved] (CONNECTORS-374) SharePoint connector's Japanese messages are not fully translated
[ https://issues.apache.org/jira/browse/CONNECTORS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-374. Resolution: Fixed r1230059. I removed the quotation marks from both files since these are no longer needed. SharePoint connector's Japanese messages are not fully translated - Key: CONNECTORS-374 URL: https://issues.apache.org/jira/browse/CONNECTORS-374 Project: ManifoldCF Issue Type: Improvement Components: SharePoint connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-374.patch SharePoint connector's Japanese message properties file should be fully translated. -- 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] [Resolved] (CONNECTORS-375) RSS connector's Japanese messages are not fully translated
[ https://issues.apache.org/jira/browse/CONNECTORS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-375. Resolution: Fixed r1230068. I removed the quotes as they are no longer needed, and restored another fix which was required to prevent the run-rss-UI-tests-derby ant target from failing. RSS connector's Japanese messages are not fully translated -- Key: CONNECTORS-375 URL: https://issues.apache.org/jira/browse/CONNECTORS-375 Project: ManifoldCF Issue Type: Improvement Components: RSS connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-375.patch Should translated RSS connector's Japanese message properties. -- 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] [Resolved] (CONNECTORS-333) Solr 3.x and 4.x plugins should use best practices in setting up http connections
[ https://issues.apache.org/jira/browse/CONNECTORS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-333. Resolution: Fixed I was able to get the CloseHook API to be used for both Plugins. This does not kill the thread, which is bound statically to the multithreaded connection manager class. The only way to kill it is to call shutdownAll(), which could blow up other things in the same JVM. Solr 3.x and 4.x plugins should use best practices in setting up http connections - Key: CONNECTORS-333 URL: https://issues.apache.org/jira/browse/CONNECTORS-333 Project: ManifoldCF Issue Type: Bug Components: Solr-3.x-component, Solr-4.x-component Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5 The Solr components need to use keep-alive in order to not accumulate handles in CLOSE_WAIT. -- 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] [Resolved] (CONNECTORS-377) Should standardize on src/main/resources in directories, Maven build, and ant build
[ https://issues.apache.org/jira/browse/CONNECTORS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-377. Resolution: Fixed Fix Version/s: ManifoldCF 0.5 r1230101 Should standardize on src/main/resources in directories, Maven build, and ant build --- Key: CONNECTORS-377 URL: https://issues.apache.org/jira/browse/CONNECTORS-377 Project: ManifoldCF Issue Type: Bug Components: Build Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 We use src/main/resource sometimes and that is going to cause nothing but trouble. We need to fix this. -- 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] [Resolved] (CONNECTORS-369) i18n/localization work for connectors often includes javascript quotes in the translated text
[ https://issues.apache.org/jira/browse/CONNECTORS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-369. Resolution: Fixed I think I've got all of these cleaned up now. As long as new contributions don't reintroduce the problem, we're all set. i18n/localization work for connectors often includes javascript quotes in the translated text - Key: CONNECTORS-369 URL: https://issues.apache.org/jira/browse/CONNECTORS-369 Project: ManifoldCF Issue Type: Task Components: File system connector, FileNet connector, GTS connector, JCIFS connector, JDBC connector, LiveLink connector, Lucene/SOLR connector, RSS connector, Web connector, Wiki connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The i18n for many of the connectors includes quotation marks that should not be in the translation, but should instead be in the code. See CONNECTORS-356 for a detailed description of the problem and the solution. -- 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] [Resolved] (CONNECTORS-363) LiveLink connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-363. Resolution: Fixed LiveLink connector should be fully I18N --- Key: CONNECTORS-363 URL: https://issues.apache.org/jira/browse/CONNECTORS-363 Project: ManifoldCF Issue Type: Improvement Components: LiveLink connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-363.patch, CONNECTORS-363.patch Should extract out all messages to properties file. -- 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] [Resolved] (CONNECTORS-372) WebCrawler connector Japanese message properties file is not fully translated
[ https://issues.apache.org/jira/browse/CONNECTORS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-372. Resolution: Fixed r1229540 WebCrawler connector Japanese message properties file is not fully translated - Key: CONNECTORS-372 URL: https://issues.apache.org/jira/browse/CONNECTORS-372 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-372.patch WebCrawler connector Japanese message files is not fully translated. -- 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] [Resolved] (CONNECTORS-357) Messages in Documentum connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-357. Resolution: Fixed Messages in Documentum connector should be fully I18N - Key: CONNECTORS-357 URL: https://issues.apache.org/jira/browse/CONNECTORS-357 Project: ManifoldCF Issue Type: Improvement Components: Documentum connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-357.patch All messages in Documentum connector should be extracted out to properties file and Japanese messages should be added. -- 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] [Resolved] (CONNECTORS-359) All messages in Filesystem connector should be extracted out to properties file
[ https://issues.apache.org/jira/browse/CONNECTORS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-359. Resolution: Fixed All messages in Filesystem connector should be extracted out to properties file --- Key: CONNECTORS-359 URL: https://issues.apache.org/jira/browse/CONNECTORS-359 Project: ManifoldCF Issue Type: Improvement Components: File system connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-359.patch To fully support I18N, all messages should be extracted out to properties file. -- 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] [Resolved] (CONNECTORS-362) JDBC connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-362. Resolution: Fixed JDBC connector should be fully I18N --- Key: CONNECTORS-362 URL: https://issues.apache.org/jira/browse/CONNECTORS-362 Project: ManifoldCF Issue Type: Improvement Components: JDBC connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-362.patch Should extract out all messages to properties file. -- 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] [Resolved] (CONNECTORS-367) WebCrawler connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-367. Resolution: Fixed WebCrawler connector should be fully I18N - Key: CONNECTORS-367 URL: https://issues.apache.org/jira/browse/CONNECTORS-367 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-367.patch Should extract all messages to properties file. -- 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] [Resolved] (CONNECTORS-365) Sharepoint connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-365. Resolution: Fixed Sharepoint connector should be fully I18N - Key: CONNECTORS-365 URL: https://issues.apache.org/jira/browse/CONNECTORS-365 Project: ManifoldCF Issue Type: Improvement Components: SharePoint connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-365.patch All messages in Sharepoint connector should be extracted out to properties file. -- 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] [Resolved] (CONNECTORS-370) Ability to pass parameters to I18N messages
[
https://issues.apache.org/jira/browse/CONNECTORS-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-370.
Resolution: Fixed
Ability to pass parameters to I18N messages
---
Key: CONNECTORS-370
URL: https://issues.apache.org/jira/browse/CONNECTORS-370
Project: ManifoldCF
Issue Type: Improvement
Components: Framework crawler agent
Affects Versions: ManifoldCF 0.5
Reporter: Hitoshi Ozawa
Assignee: Karl Wright
Priority: Minor
Labels: I18N
Fix For: ManifoldCF 0.5
Current I18N scheme only allows one sequential set of words to be extracted
out to properties file.
Some languages such as Japanese have different grammerical syntax than
English may require parameters to be passed in different order.
Would like to have ability to pass parameters to messages in properties file:
e.g.
message1={$1} with match parameters {$2} and {$3} resulted in {$4}
--
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] [Resolved] (CONNECTORS-318) Make it easier to trace XML parsing errors
[
https://issues.apache.org/jira/browse/CONNECTORS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-318.
Resolution: Fixed
r1228768
Make it easier to trace XML parsing errors
--
Key: CONNECTORS-318
URL: https://issues.apache.org/jira/browse/CONNECTORS-318
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.5
Reporter: Martin Goldhahn
Assignee: Karl Wright
Priority: Minor
Fix For: ManifoldCF 0.5
Attachments: XMLDoc.java.patch
I had a hard time tracking an erroneous response from Solr. All I got was
something like this:
{{[Fatal Error] :112:120: The element type HR must be terminated by the
matching end-tag /HR.}}
There was no indication what the error was an what component issued the error.
--
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] [Resolved] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-258. Resolution: Fixed The mvn-bootstrap .sh/.bat has been part of manifoldcf since the 0.3 release. pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Assignee: Karl Wright Priority: Minor Labels: maven Fix For: ManifoldCF 0.3 Attachments: mvn-bootstrap.sh Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- 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] [Resolved] (CONNECTORS-342) File connector Paths tab has broken html
[ https://issues.apache.org/jira/browse/CONNECTORS-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-342. Resolution: Fixed File connector Paths tab has broken html -- Key: CONNECTORS-342 URL: https://issues.apache.org/jira/browse/CONNECTORS-342 Project: ManifoldCF Issue Type: Bug Components: File system connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.4 The file system connector has broken HTML for the Paths tab, which blocks people from using the connector. -- 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] [Resolved] (CONNECTORS-352) logfile property is written twice in properties.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-352. Resolution: Fixed Fix Version/s: ManifoldCF 0.5 logfile property is written twice in properties.xml --- Key: CONNECTORS-352 URL: https://issues.apache.org/jira/browse/CONNECTORS-352 Project: ManifoldCF Issue Type: Bug Components: Tests Reporter: Martin Goldhahn Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-352.patch -- 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] [Resolved] (CONNECTORS-346) Testing hierarchy needs work
[ https://issues.apache.org/jira/browse/CONNECTORS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-346. Resolution: Fixed r1226141 completes the changes Testing hierarchy needs work Key: CONNECTORS-346 URL: https://issues.apache.org/jira/browse/CONNECTORS-346 Project: ManifoldCF Issue Type: Task Components: Tests Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The testing hierarchy is in need of some work. Specifically: - Load tests should be pulled back into the tests directory, if possible, and given a suffix (LT?) which allows Maven to skip them by default. This will simplify the ant build.xml too. - Final ant targets (test-dr, load-dr, UI, etc.) need to be regularized. They all should begin with test, for one thing. I don't yet have a proposal though. - There's a lot of code duplication in the hierarchy and across the different database base classes. For example, methods that talk with the API appear in the base class for each database, and could be shared if there was such a thing as multiple inheritance. Since there isn't we could instead pull these into their own support class, like HTMLTester does for the UI stuff. -- 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] [Resolved] (CONNECTORS-337) Maven build -DskipIT does not seem to skip integration tests anymore
[ https://issues.apache.org/jira/browse/CONNECTORS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-337. Resolution: Fixed Assignee: Karl Wright Maven build -DskipIT does not seem to skip integration tests anymore Key: CONNECTORS-337 URL: https://issues.apache.org/jira/browse/CONNECTORS-337 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 mvn clean -DskipIT install still seems to run all the integration tests. -- 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] [Resolved] (CONNECTORS-334) Make ManifoldCF fully run on MySQL
[ https://issues.apache.org/jira/browse/CONNECTORS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-334. Resolution: Fixed Make ManifoldCF fully run on MySQL -- Key: CONNECTORS-334 URL: https://issues.apache.org/jira/browse/CONNECTORS-334 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Make ManifoldCF run properly on top of MySQL. The ticket should be viewed as a combination of the MySQL contributions from CONNECTORS-314, plus tests and other changes needed to make MySQL be a viable option for crawling. -- 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] [Resolved] (CONNECTORS-332) Multiprocess example might benefit from a multiprocess jetty runner, started by a script
[ https://issues.apache.org/jira/browse/CONNECTORS-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-332. Resolution: Fixed Multiprocess example might benefit from a multiprocess jetty runner, started by a script Key: CONNECTORS-332 URL: https://issues.apache.org/jira/browse/CONNECTORS-332 Project: ManifoldCF Issue Type: Improvement Components: Examples Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Currently the multiprocess example presumes you will start your web applications on Tomcat. It would be convenient and demonstrative, though, to have a Jetty-based way of running those web applications within the confines of the example. -- 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] [Resolved] (CONNECTORS-315) Update binary versions of plugin packages in ManifoldCF when plugins are officially released
[ https://issues.apache.org/jira/browse/CONNECTORS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-315. Resolution: Fixed Update binary versions of plugin packages in ManifoldCF when plugins are officially released Key: CONNECTORS-315 URL: https://issues.apache.org/jira/browse/CONNECTORS-315 Project: ManifoldCF Issue Type: Task Components: Lucene/SOLR connector, Meridio connector, SharePoint connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 ManifoldCF 0.4 should only include released versions of plugins. -- 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] [Resolved] (CONNECTORS-319) AgentRun command needs a shutdown hook
[ https://issues.apache.org/jira/browse/CONNECTORS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-319. Resolution: Fixed AgentRun command needs a shutdown hook -- Key: CONNECTORS-319 URL: https://issues.apache.org/jira/browse/CONNECTORS-319 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The AgentRun command does not clean up its agent running lock on ^C. This means you always have to do a lock clean if you ^C the agents process in a multi-process environment. I believe that everything else that needs a shutdown hook has one. -- 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] [Resolved] (CONNECTORS-321) Every other time a multiprocess initialization script is run using HSQLDB, a nonsense database exception occurs
[ https://issues.apache.org/jira/browse/CONNECTORS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-321. Resolution: Fixed Every other time a multiprocess initialization script is run using HSQLDB, a nonsense database exception occurs --- Key: CONNECTORS-321 URL: https://issues.apache.org/jira/browse/CONNECTORS-321 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.4 The script is the multiprocess-example initialize script. Here's the exception: Successfully registered output connector 'org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnector'org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database exception: Exception doing query: user lacks privilege or object not found: OUTPUTCONNECTORS at org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:672) at org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Database.java:700) at org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.create(Database.java:1363) at org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144) at org.apache.manifoldcf.core.database.Database.executeQuery(Database.java:179) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:771) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performLock(DBInterfaceHSQLDB.java:213) at org.apache.manifoldcf.core.database.BaseTable.performLock(BaseTable.java:65) at org.apache.manifoldcf.agents.outputconnmgr.OutputConnectorManager.registerConnector(OutputConnectorManager.java:161) at org.apache.manifoldcf.crawler.RegisterConnectors.registerConnectors(RegisterConnectors.java:250) at org.apache.manifoldcf.crawler.InitializeAndRegister.doExecute(InitializeAndRegister.java:56) at org.apache.manifoldcf.crawler.InitializeAndRegister.main(InitializeAndRegister.java:73) Caused by: java.sql.SQLException: user lacks privilege or object not found: OUTPUTCONNECTORS at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1838) at org.hsqldb.jdbc.JDBCStatement.execute(JDBCStatement.java:636) at org.apache.manifoldcf.core.database.Database.execute(Database.java:777) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:632) -- 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] [Resolved] (CONNECTORS-320) DBCreate on HSQLDB instance operating in external mode fails second time
[ https://issues.apache.org/jira/browse/CONNECTORS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-320. Resolution: Fixed DBCreate on HSQLDB instance operating in external mode fails second time Key: CONNECTORS-320 URL: https://issues.apache.org/jira/browse/CONNECTORS-320 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker Fix For: ManifoldCF 0.4 When ManifoldCF is configured to run HSQLDB, if you try to create the database twice you get an exception. This is used during upgrades. PostgreSQL works fine here. The exception is: C:\wip\mcf\CONNECTORS-313\dist\multiprocess-exampleinitialize.bat Configuration file successfully read org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database exception: E xception doing query: object name already exists: DBNAME at org.apache.manifoldcf.core.database.Database.executeViaThread(Databas e.java:672) at org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Dat abase.java:716) at org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.creat e(Database.java:1363) at org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndEx ecute(CacheManager.java:144) at org.apache.manifoldcf.core.database.Database.executeQuery(Database.ja va:179) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.createUserAndDa tabase(DBInterfaceHSQLDB.java:621) at org.apache.manifoldcf.core.system.ManifoldCF.createSystemDatabase(Man ifoldCF.java:683) at org.apache.manifoldcf.crawler.RegisterConnectors.createDatabaseAndSch ema(RegisterConnectors.java:71) at org.apache.manifoldcf.crawler.RegisterAll.doExecute(RegisterAll.java: 33) at org.apache.manifoldcf.crawler.TransactionalCrawlerInitializationComma nd.execute(TransactionalCrawlerInitializationCommand.java:43) at org.apache.manifoldcf.crawler.RegisterAll.main(RegisterAll.java:55) Caused by: java.sql.SQLException: object name already exists: DBNAME at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1838) at org.hsqldb.jdbc.JDBCStatement.execute(JDBCStatement.java:636) at org.apache.manifoldcf.core.database.Database.execute(Database.java:77 7) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(D atabase.java:632) -- 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] [Resolved] (CONNECTORS-313) An example multi-process properties.xml delivered to the dist folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-313. Resolution: Fixed An example multi-process properties.xml delivered to the dist folder would be very helpful Key: CONNECTORS-313 URL: https://issues.apache.org/jira/browse/CONNECTORS-313 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, register-draft.sh The multiprocess setup does not have an example properties.xml file. We should deliver one, in the right place so that all the scripts find it (the dist directory). It would also be helpful to deliver into this directory scripts for: - Registering all the connectors that were built - Starting the agents process -- 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] [Resolved] (CONNECTORS-316) Update all version numbers to 0.5
[ https://issues.apache.org/jira/browse/CONNECTORS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-316. Resolution: Fixed r1214402 Update all version numbers to 0.5 - Key: CONNECTORS-316 URL: https://issues.apache.org/jira/browse/CONNECTORS-316 Project: ManifoldCF Issue Type: Task Components: Build, Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Documentation and version numbers all need updating, now that 0.4-incubating has branched. -- 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] [Resolved] (CONNECTORS-310) Maven build of Alfresco connector fails
[
https://issues.apache.org/jira/browse/CONNECTORS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-310.
Resolution: Fixed
Changed mvn-bootstrap to import the missing jars, all except bouncycastle.
There's a 140 version on maven that I just used instead.
Maven build of Alfresco connector fails
---
Key: CONNECTORS-310
URL: https://issues.apache.org/jira/browse/CONNECTORS-310
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector, Build
Affects Versions: ManifoldCF 0.4
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
Fix For: ManifoldCF 0.4
When I try mvn clean install on trunk, I get the following error:
{code}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ManifoldCF SUCCESS [0.752s]
[INFO] ManifoldCF - Framework SUCCESS [0.099s]
[INFO] ManifoldCF - Framework - Core . SUCCESS [3.788s]
[INFO] ManifoldCF - Framework - UI Core .. SUCCESS [1.327s]
[INFO] ManifoldCF - Framework - Agents ... SUCCESS [12.891s]
[INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [19.641s]
[INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.089s]
[INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.209s]
[INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.296s]
[INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.148s]
[INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [5.093s]
[INFO] ManifoldCF - Framework - Script Engine SUCCESS [6.514s]
[INFO] ManifoldCF - Connectors ... SUCCESS [0.075s]
[INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.702s]
[INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [12.696s]
[INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.450s]
[INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [1.638s]
[INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.560s]
[INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.332s]
[INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.027s]
[INFO] ManifoldCF - Connectors - RSS . SUCCESS [2.727s]
[INFO] ManifoldCF - Connectors - Solr SUCCESS [1.474s]
[INFO] ManifoldCF - Connectors - Web . SUCCESS [3.440s]
[INFO] ManifoldCF - Connectors - CMIS SUCCESS [16.662s]
[INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [2.050s]
[INFO] ManifoldCF - Connectors - Wiki SUCCESS [12.567s]
[INFO] ManifoldCF - Connectors - Alfresco FAILURE [2:15.432s]
[INFO] ManifoldCF - Test materials ... SKIPPED
[INFO] ManifoldCF - Test Materials - Alfresco WAR SKIPPED
[INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
[INFO] ManifoldCF - Tests 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]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4:15.090s
[INFO] Finished at: Thu Dec 08 03:43:10 EST 2011
[INFO] Final Memory: 72M/181M
[INFO]
[ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
reso
lve dependencies for project
org.apache.manifoldcf:mcf-alfresco-connector:jar:0.
4.0-SNAPSHOT: The following artifacts could not be resolved:
org.opensaml:opensa
ml:jar:1.0.1, bouncycastle:bcprov-jdk15:jar:137,
xml-security:xmlsec:jar:1.4.1:
Could not find artifact org.opensaml:opensaml:jar:1.0.1 in alfresco-public
(http
://maven.alfresco.com/nexus/content/groups/public) - [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
[jira] [Resolved] (CONNECTORS-308) ant test fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-308.
Resolution: Fixed
Giving more memory to the test JVM did the trick.
ant test fails due to Alfresco test problem
-
Key: CONNECTORS-308
URL: https://issues.apache.org/jira/browse/CONNECTORS-308
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector
Affects Versions: ManifoldCF 0.4
Environment: Windows (although this shouldn't matter)
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
Fix For: ManifoldCF 0.4
I get this error when I do ant test:
{code}
...
setup-alfresco-connector-tests:
[copy] Copying 6 files to C:\wip\mcf\trunk\connectors\alfresco\lib
BUILD FAILED
C:\wip\mcf\trunk\build.xml:316: The following error occurred while executing
this line:
C:\wip\mcf\trunk\tests\alfresco-war\build.xml:25: The following error
occurred while executing this line:
C:\wip\mcf\trunk\tests\alfresco-war\tools\ant\tasks\tomcat-tasks.xml:30:
C:\wip\mcf\trunk\${appserver.dir}\server\lib does not exist.
Total time: 18 seconds
C:\wip\mcf\trunk
{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] [Resolved] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-287. Resolution: Fixed This looks completed to me. An Alfresco connector would be helpful -- Key: CONNECTORS-287 URL: https://issues.apache.org/jira/browse/CONNECTORS-287 Project: ManifoldCF Issue Type: New Feature Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.4 Attachments: Typetab.png Original Estimate: 120h Remaining Estimate: 120h The idea of this connector is based on the fact that there are many Alfresco installations that don't yet support the CMIS protocol (2.1-2.9). I'm starting to think about the Alfresco Repository Connector. Alfresco doesn't expose any REST API to execute Lucene queries without adding some custom WebScripts. I would like to implement a connector that doesn't need to install any other custom plugin and that it can work with any Alfresco 2.x out of the box installation. The unique search service exposed by Alfresco via REST is a keyword search service, but it is not useful for our connector. I think that the right way to follow is to use the Alfresco Web Services API, this API is based on the SOAP protocol and we have a specific Alfresco Web Services Client provided by Alfresco. -- 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] [Resolved] (CONNECTORS-284) HSQLDB load test runs out of memory and has lots of very slow queries
[ https://issues.apache.org/jira/browse/CONNECTORS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-284. Resolution: Fixed r1210307. HSQLDB load test runs out of memory and has lots of very slow queries - Key: CONNECTORS-284 URL: https://issues.apache.org/jira/browse/CONNECTORS-284 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 Some of the long-running queries are as follows: - document stuffer query - locating carrydown information -- 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] [Resolved] (CONNECTORS-299) Crawling using Postgresql 9.1 hangs occasionally for a while
[ https://issues.apache.org/jira/browse/CONNECTORS-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-299. Resolution: Fixed Crawling using Postgresql 9.1 hangs occasionally for a while Key: CONNECTORS-299 URL: https://issues.apache.org/jira/browse/CONNECTORS-299 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The hang takes place because of this postgresql error: ERROR 2011-11-28 14:46:23,959 (Worker thread '25') - Worker thread aborting and restarting due to database connection reset: Database exception: Exception doing query: ERROR: could not serialize access due to read/write dependencies among transactions Detail: Reason code: Canceled on identification as a pivot, during commit attempt. Hint: The transaction might succeed if retried. org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database exception: Exception doing query: ERROR: could not serialize access due to read/write dependencies among transactions Detail: Reason code: Canceled on identification as a pivot, during commit attempt. Hint: The transaction might succeed if retried. at org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:608) at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.commitCurrentTransaction(DBInterfacePostgreSQL.java:1141) at org.apache.manifoldcf.core.database.Database.endTransaction(Database.java:321) at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.endTransaction(DBInterfacePostgreSQL.java:1112) at org.apache.manifoldcf.crawler.jobs.JobManager.finishDocuments(JobManager.java:4072) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:567) Caused by: org.postgresql.util.PSQLException: ERROR: could not serialize access due to read/write dependencies among transactions This is happening during the commit phase of the transaction, at a point where none of the transaction blocks in ManifoldCF know to look for it. It is therefore likely that all transaction blocks throughout ManifoldCF that deal with deadlock will need to be changed. -- 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] [Resolved] (CONNECTORS-298) Web connector: SSL trust error message highly misleading
[ https://issues.apache.org/jira/browse/CONNECTORS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-298. Resolution: Fixed r1208226 improves the message Web connector: SSL trust error message highly misleading Key: CONNECTORS-298 URL: https://issues.apache.org/jira/browse/CONNECTORS-298 Project: ManifoldCF Issue Type: Bug Components: Web connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.4 When crawling learningresources.nga.gov, the web connector gets a strange exception from certificate verification logic in Sun's SSL implementation. Here's the trace: INFO 2011-11-29 20:13:33,397 (Thread-535) - I/O exception (javax.net.ssl.SSLException) caught when processing request: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty DEBUG 2011-11-29 20:13:33,397 (Thread-535) - java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1649) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1612) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1595) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1521) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:64) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(Unknown Source) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.flushRequestOutputStream(Unknown Source) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(Unknown Source) at org.apache.commons.httpclient.HttpMethodBase.execute(Unknown Source) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source) at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source) at org.apache.manifoldcf.crawler.connectors.webcrawler.ThrottledFetcher$ThrottledConnection$ExecuteMethodThread.run(ThrottledFetcher.java:1244) Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty at sun.security.validator.PKIXValidator.init(PKIXValidator.java:57) at sun.security.validator.Validator.getInstance(Validator.java:161) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:108) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:204) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1185) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:893) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:632) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) ... 10 more -- 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] [Resolved] (CONNECTORS-272) Upgrade PostgreSQL to version 9.1
[ https://issues.apache.org/jira/browse/CONNECTORS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-272. Resolution: Fixed Upgrade PostgreSQL to version 9.1 - Key: CONNECTORS-272 URL: https://issues.apache.org/jira/browse/CONNECTORS-272 Project: ManifoldCF Issue Type: Task Components: Framework core Reporter: Erlend Garåsen Assignee: Erlend Garåsen Fix For: ManifoldCF 0.4 The recommended versions of PostgreSQL for ManifoldCF are 8.3 og 8.4. Since the latter version was released in July 2009, we should consider an upgrade to PostgreSQL 9.1. PostgreSQL 9.1 has several changes, for example improved VACUUM functions which may make ManifoldCF more efficient (see E.8.3.4.3): http://www.postgresql.org/docs/9.1/static/release.html The JDBC driver which ships with ManifoldCF should probably be upgraded, but we need to figure out whether the newest JDBC driver is backward compatible with PostgreSQL 8.x. -- 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] [Resolved] (CONNECTORS-293) missing samba version dependency on the last trunk
[ https://issues.apache.org/jira/browse/CONNECTORS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-293. Resolution: Fixed Fix Version/s: ManifoldCF 0.4 Assignee: Karl Wright missing samba version dependency on the last trunk -- Key: CONNECTORS-293 URL: https://issues.apache.org/jira/browse/CONNECTORS-293 Project: ManifoldCF Issue Type: Bug Components: JCIFS connector Affects Versions: ManifoldCF 0.4 Environment: java 6, maven 3.0.3, Manifold trunk from http://svn.apache.org/repos/asf/incubator/lcf/trunk Reporter: Luca Stancapiano Assignee: Karl Wright Fix For: ManifoldCF 0.4 building the jcifs project, it doesn't find the samba dependency from maven. It requests a 1.3.17 version. I find only 1.3.14 and 1.3.3. Maybe this jar should be added in the documentation where the external dependencies are listed. Here the error executing the command 'mvn install -Dmaven.test.skip': [ERROR] Failed to execute goal on project mcf-jcifs-connector: Could not resolve dependencies for project org.apache.manifoldcf:mcf-jcifs-connector:jar:0.4.0-SNAPSHOT: Failure to find org.samba.jcifs:jcifs:jar:1.3.17 in xx was cached in the local repository, resolution will not be reattempted until the update interval of sose-private has elapsed or updates are forced - [Help 1] -- 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] [Resolved] (CONNECTORS-291) Active Directory authority fails to recover from error gracefully
[ https://issues.apache.org/jira/browse/CONNECTORS-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-291. Resolution: Fixed Active Directory authority fails to recover from error gracefully - Key: CONNECTORS-291 URL: https://issues.apache.org/jira/browse/CONNECTORS-291 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-291.patch When the active directory authority gets an error during ctx.reconnect(), it seems to be put into a state where it doesn't recover until 5 minutes go by (that is until the LdapContext is flushed). It really needs to drop the LDAP context at that point and start fresh immediately. -- 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] [Resolved] (CONNECTORS-290) Stuffer query will perform poorly under some conditions
[ https://issues.apache.org/jira/browse/CONNECTORS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-290. Resolution: Fixed Stuffer query will perform poorly under some conditions --- Key: CONNECTORS-290 URL: https://issues.apache.org/jira/browse/CONNECTORS-290 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3, ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The stuffer query, which returns documents in index order by docpriority for processing, performs poorly when lots of documents are in the queue and have a good priority but can't be taken because of job state. This can happen when: (1) a large job is aborted, leaving lots of jobqueue records with docpriority values around; (2) a job is paused for an extended period of time, while others are running. In the second case, when the paused job is resumed, there's an added problem because, for a while, only documents from the paused job will be processed. The answer to (1) may well be to clean out all docpriority values on job abort. Right now there is no logic that sets docpriority values to null, but there clearly needs to be, or the docpriority index will remain polluted with rows that must be scanned but cannot be used for an extended period of time. The correct answer to (2) is to clear out docpriority values when a job is paused, and then redo them all when the job is resumed. Similarly, docpriority values should be set for all of a job's documents when a job is started, and should be nulled out when documents enter non-active states. The former currently occurs, but not the latter. -- 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] [Resolved] (CONNECTORS-209) HSQLDB driver does not know how to deal with remote HSQLDB instances
[ https://issues.apache.org/jira/browse/CONNECTORS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-209. Resolution: Fixed r1201399. Still need to fix CONNECTORS-284 however. HSQLDB driver does not know how to deal with remote HSQLDB instances Key: CONNECTORS-209 URL: https://issues.apache.org/jira/browse/CONNECTORS-209 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.4 The HSQLDB driver only knows how to work with local instances of HSQLDB. This could be readily changed. According to the HSQLDB team: Regarding deployment options, HSQLDB is not just for embedded use and can easily be run as a server. It would be nice if manifoldCF db access does not inadvertently prevent this. So long as the url is not edited by manifoldCF, the user can replace it with a client/server URL. URL for embedded jdbc:hsqldb:file:file path;hsqldb.shutdown=true URL for client server jdbc:hsqldb:hsql:server name and port/dbname URL for client server when server allows remote opening of databases jdbc:hsqldb:hsql:server name and port/dbname;file:file path -- 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] [Resolved] (CONNECTORS-285) JobManager getStatus() command always performs slow queries, even when they may not be needed
[ https://issues.apache.org/jira/browse/CONNECTORS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-285. Resolution: Fixed r1198541. JobManager getStatus() command always performs slow queries, even when they may not be needed - Key: CONNECTORS-285 URL: https://issues.apache.org/jira/browse/CONNECTORS-285 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The JobManager.getStatus() method, and the associated API operation, always obtain the counts of documents processed or in progress. These queries are slow and don't scale because they require sequential scan of the jobqueue. Sometimes all that is needed is just the status of the job. We should have a way of getting that that is performant. -- 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] [Resolved] (CONNECTORS-100) DB lock timeout, and/or indefinite or excessive database activity
[
https://issues.apache.org/jira/browse/CONNECTORS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-100.
Resolution: Fixed
DB lock timeout, and/or indefinite or excessive database activity
-
Key: CONNECTORS-100
URL: https://issues.apache.org/jira/browse/CONNECTORS-100
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3,
ManifoldCF 0.4
Environment: Running unmodified dist/example from trunk/ using the
default configuration.
Reporter: Andrzej Bialecki
Assignee: Karl Wright
Fix For: ManifoldCF 0.4
When a job is started and running (via crawler-ui) occasionally it's not
possible to display a list of running jobs. The problem persists even after
restarting ACF. The following exception is thrown in the console:
{code}
org.apache.acf.core.interfaces.ACFException: Database exception: Exception
doing query: A lock could not be obtained within the time requested
at
org.apache.acf.core.database.Database.executeViaThread(Database.java:421)
at
org.apache.acf.core.database.Database.executeUncachedQuery(Database.java:465)
at
org.apache.acf.core.database.Database$QueryCacheExecutor.create(Database.java:1072)
at
org.apache.acf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
at
org.apache.acf.core.database.Database.executeQuery(Database.java:167)
at
org.apache.acf.core.database.DBInterfaceDerby.performQuery(DBInterfaceDerby.java:727)
at
org.apache.acf.crawler.jobs.JobManager.makeJobStatus(JobManager.java:5611)
at
org.apache.acf.crawler.jobs.JobManager.getAllStatus(JobManager.java:5549)
at
org.apache.jsp.showjobstatus_jsp._jspService(showjobstatus_jsp.java:316)
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:377)
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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.sql.SQLTransactionRollbackException: A lock could not be
obtained within the time requested
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.acf.core.database.Database.execute(Database.java:526)
at
[jira] [Resolved] (CONNECTORS-281) RSS connector takes nearly a second to fetch a document even with no throttling
[ https://issues.apache.org/jira/browse/CONNECTORS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-281. Resolution: Fixed RSS connector takes nearly a second to fetch a document even with no throttling --- Key: CONNECTORS-281 URL: https://issues.apache.org/jira/browse/CONNECTORS-281 Project: ManifoldCF Issue Type: Bug Components: RSS connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The RSS connector load test shows that the RSS connector is overthrottling, for some reason. 10-24-2011 05:30:50.423 fetch http://localhost:8189/rss/gen.php?doc=4feed=782type=doc 200 46 843 ... Where 843 ms is taken to fetch a document of size 46 bytes. This is with connection parameters as follows: Parameters: Robots usage=none Max fetches per minute=100 Email address=someb...@somewhere.com KB per second=100 Max server connections=100 -- 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] [Resolved] (CONNECTORS-282) We see a lot of unique constraint collisions trying to insert into the ingeststatus table
[ https://issues.apache.org/jira/browse/CONNECTORS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-282. Resolution: Fixed Assignee: Karl Wright r1188611. We see a lot of unique constraint collisions trying to insert into the ingeststatus table - Key: CONNECTORS-282 URL: https://issues.apache.org/jira/browse/CONNECTORS-282 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.4 Postgresql logs the following over and over: 2011-10-24 23:48:56 EDT STATEMENT: INSERT INTO ingeststatus (id,changecount,dockey,lastversion,firstingest,connectionname,authorityname,urihash,lastoutputversion,lastingest,docuri) VALUES ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11) This is clearly part of a failback sequence designed to prevent duplicates, but we seem to be erring by trying the least probable thing first. This no doubt impacts performance as well. -- 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] [Resolved] (CONNECTORS-280) When job deletion has started, but job is not yet deleting documents, Not yet run is displayed on status page
[ https://issues.apache.org/jira/browse/CONNECTORS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-280. Resolution: Fixed r1187210. When job deletion has started, but job is not yet deleting documents, Not yet run is displayed on status page --- Key: CONNECTORS-280 URL: https://issues.apache.org/jira/browse/CONNECTORS-280 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 Not yet run is displayed but the correct status should be something else. The job's status value is V, which corresponds to state DELETESTARTINGUP. -- 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] [Resolved] (CONNECTORS-277) WikiConnector - option to limit crawl by namespace
[ https://issues.apache.org/jira/browse/CONNECTORS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-277. Resolution: Fixed r1187038 WikiConnector - option to limit crawl by namespace -- Key: CONNECTORS-277 URL: https://issues.apache.org/jira/browse/CONNECTORS-277 Project: ManifoldCF Issue Type: Improvement Components: Wiki connector Affects Versions: ManifoldCF 0.4 Reporter: Tobias Wunderlich Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.4 At the moment, the WikiConnector crawls the whole Wiki. This can take up a lot of time. For testing purposes an option to limit the pages to crawl by namespaces(title) would be great. Tobias -- 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] [Resolved] (CONNECTORS-187) WorkerThread method processDeleteList does not handle ServiceInterruptions from output connector optimally
[ https://issues.apache.org/jira/browse/CONNECTORS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-187. Resolution: Fixed r1184833. WorkerThread method processDeleteList does not handle ServiceInterruptions from output connector optimally -- Key: CONNECTORS-187 URL: https://issues.apache.org/jira/browse/CONNECTORS-187 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The processDeleteList method in WorkerThread does not handle ServiceInterruption exceptions optimally; it just waits five minutes and retries. What it should do is requeue all the affected documents for the prescribed time, ignoring the possibility of failure or skip, since neither of these can be performed when the output connection is not working. -- 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
