[jira] Created: (CONNECTORS-162) To support connectors that have their own class loaders, we need to provide a way of creating derivative resource loaders

URL: https://issues.apache.org/jira/browse/CONNECTORS-162 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright ManifoldCF currently creates

[jira] Resolved: (CONNECTORS-162) To support connectors that have their own class loaders, we need to provide a way of creating derivative resource loaders

[ https://issues.apache.org/jira/browse/CONNECTORS-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-162. Resolution: Fixed Fix Version/s: ManifoldCF next r1072823. To support

[jira] Created: (CONNECTORS-163) Go to current version of Derby, to try and avoid internal deadlocks

Type: Improvement Components: Framework core Affects Versions: ManifoldCF next Reporter: Karl Wright Derby 10.5.3.0 internally deadlocks on the straightforward correlated subqueries involving the carrydown table. The source of the problem is not clear. However

[jira] Created: (CONNECTORS-165) Upgrade to jetty 6.1.26, with patches, for latest unicode support etc.

Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Priority: Minor The version of jetty we're using is pretty old. Solr is upgrading to 6.1.26, plus some patches. We

[jira] Resolved: (CONNECTORS-165) Upgrade to jetty 6.1.26, with patches, for latest unicode support etc.

[ https://issues.apache.org/jira/browse/CONNECTORS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-165. Resolution: Fixed Fix Version/s: ManifoldCF next r1074713. Upgrade to jetty

[jira] Created: (CONNECTORS-166) Crawl seizes up when running Derby

Affects Versions: ManifoldCF 0.1, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright A crawl using multiple worker threads with Derby eventually hangs, because threads get deadlocked dealing with carrydown information. At the time of hang, a thread dump yields

[jira] Assigned: (CONNECTORS-159) Support for external PostgreSQL server

[ https://issues.apache.org/jira/browse/CONNECTORS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-159: -- Assignee: Karl Wright Support for external PostgreSQL server

[jira] Updated: (CONNECTORS-159) Support for external PostgreSQL server

[ https://issues.apache.org/jira/browse/CONNECTORS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-159: --- Resolution: Fixed Status: Resolved (was: Patch Available) r1078003, slightly

[jira] Commented: (CONNECTORS-166) Crawl seizes up when running Derby

[ https://issues.apache.org/jira/browse/CONNECTORS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006583#comment-13006583 ] Karl Wright commented on CONNECTORS-166: According to the Derby team, Derby

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

[ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-168: --- Fix Version/s: ManifoldCF 0.2 Status: Patch Available (was: Open) This patch

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

[ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-168: --- Comment: was deleted (was: This patch should allow the raw stack trace and error

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

[ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-168: --- Status: Open (was: Patch Available) Solr connector does not handle 500 errors well

[jira] Resolved: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

[ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-168. Resolution: Fixed r1081809. Solr connector does not handle 500 errors well

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13007773#comment-13007773 ] Karl Wright commented on CONNECTORS-100: Confirmed. It's not an actual

[jira] Created: (CONNECTORS-169) Maximum OR clause constant not present in database abstraction

Components: Framework core Affects Versions: ManifoldCF 0.2 Reporter: Karl Wright Assignee: Karl Wright There's a maximum IN clause constant in IDBInterface, but the maximum OR clause number is hardwired, and is strewn throughout the code. That makes

[jira] Created: (CONNECTORS-170) Derby database driver needs to periodically update statistics

Components: Framework core Affects Versions: ManifoldCF 0.2 Reporter: Karl Wright The Derby database driver needs to update statistics periodically, using logic similar to that developed for PostgreSQL. The way that's done is through calling

[jira] Assigned: (CONNECTORS-170) Derby database driver needs to periodically update statistics

[ https://issues.apache.org/jira/browse/CONNECTORS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-170: -- Assignee: Karl Wright Derby database driver needs to periodically update

[jira] Resolved: (CONNECTORS-169) Maximum OR clause constant not present in database abstraction

[ https://issues.apache.org/jira/browse/CONNECTORS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-169. Resolution: Fixed Fix Version/s: ManifoldCF 0.2 r1082484. Maximum OR clause

[jira] Resolved: (CONNECTORS-170) Derby database driver needs to periodically update statistics

[ https://issues.apache.org/jira/browse/CONNECTORS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-170. Resolution: Fixed Fix Version/s: ManifoldCF 0.2 r1082598. Derby database

[jira] [Created] (CONNECTORS-172) Intermittent test failures

Reporter: Karl Wright Priority: Minor The Derby filesystem end-to-end tests sometimes randomly fail with a Database error: No existing connection error during a job status wait. Not sure what's happening here, but they succeed much of the time. There's not much of a hint

[jira] [Updated] (CONNECTORS-171) RSS Connector dechromed mode can corrupt data prior to indexing

[ https://issues.apache.org/jira/browse/CONNECTORS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-171: --- Resolution: Fixed Fix Version/s: ManifoldCF next Assignee: Karl Wright

[jira] [Commented] (CONNECTORS-173) Table Entity on javadoc

[ https://issues.apache.org/jira/browse/CONNECTORS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013910#comment-13013910 ] Karl Wright commented on CONNECTORS-173: Offhand, these look good. I'll have

[jira] [Commented] (CONNECTORS-173) Table Entity on javadoc

[ https://issues.apache.org/jira/browse/CONNECTORS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013964#comment-13013964 ] Karl Wright commented on CONNECTORS-173: I'll be pushing the newer javadocs

[jira] [Commented] (CONNECTORS-172) Intermittent test failures

[ https://issues.apache.org/jira/browse/CONNECTORS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014098#comment-13014098 ] Karl Wright commented on CONNECTORS-172: Seems to be a Derby problem. DERBY

[jira] [Updated] (CONNECTORS-172) Intermittent test failures

[ https://issues.apache.org/jira/browse/CONNECTORS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-172: --- Priority: Blocker (was: Minor) Intermittent test failures

[jira] [Resolved] (CONNECTORS-172) Intermittent test failures

[ https://issues.apache.org/jira/browse/CONNECTORS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-172. Resolution: Fixed Fix Version/s: ManifoldCF next ManifoldCF

[jira] [Created] (CONNECTORS-175) The site documentation property list does not include the PostgreSQL-specific parameters, and may be missing some of the Derby ones too

: CONNECTORS-175 URL: https://issues.apache.org/jira/browse/CONNECTORS-175 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor

[jira] [Created] (CONNECTORS-176) It might be nice to have a direct link from the site menu bar to the performance tuning page

-176 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor The only way to get to the performance tuning page now is through the developer support page

[jira] [Updated] (CONNECTORS-176) It might be nice to have a direct link from the site navigation area to the performance tuning page

[ https://issues.apache.org/jira/browse/CONNECTORS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-176: --- Summary: It might be nice to have a direct link from the site navigation area

[jira] [Commented] (CONNECTORS-92) Move from ant to maven or other build system with decent library management

[ https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015008#comment-13015008 ] Karl Wright commented on CONNECTORS-92: --- This issue has stalled. The work done

[jira] [Updated] (CONNECTORS-58) ManifoldCF scripting language and some example scripts, executed via the API, plus example jobs for file system and web crawl

[ https://issues.apache.org/jira/browse/CONNECTORS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-58: -- Summary: ManifoldCF scripting language and some example scripts, executed via the API, plus

[jira] [Updated] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby

[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-110: --- Summary: Max activity and Max bandwidth reports don't work properly under Derby

[jira] [Updated] (CONNECTORS-55) Bundle database server with ManifoldCF packaged product

[ https://issues.apache.org/jira/browse/CONNECTORS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-55: -- Summary: Bundle database server with ManifoldCF packaged product (was: Bundle database

[jira] [Updated] (CONNECTORS-120) Port all connectors to use httpclient 4.x, after we submit our remaining 3.x changes as commons-httpclient tickets

[ https://issues.apache.org/jira/browse/CONNECTORS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-120: --- Summary: Port all connectors to use httpclient 4.x, after we submit our remaining 3.x

[jira] [Created] (CONNECTORS-177) File System Connector has some testing code in it

Components: File system connector Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor The file system connector has testing code in it that should be removed. See getBinNames(). -- This message is automatically generated by JIRA. For more information

[jira] [Assigned] (CONNECTORS-175) The site documentation property list does not include the PostgreSQL-specific parameters, and may be missing some of the Derby ones too

[ https://issues.apache.org/jira/browse/CONNECTORS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-175: -- Assignee: Karl Wright The site documentation property list does not include

[jira] [Resolved] (CONNECTORS-175) The site documentation property list does not include the PostgreSQL-specific parameters, and may be missing some of the Derby ones too

[ https://issues.apache.org/jira/browse/CONNECTORS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-175. Resolution: Fixed Fix Version/s: ManifoldCF next r1089704. The site

[jira] [Resolved] (CONNECTORS-179) IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't

[ https://issues.apache.org/jira/browse/CONNECTORS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-179. Resolution: Fixed Fix Version/s: ManifoldCF next r1092566 IConnector

[jira] [Commented] (CONNECTORS-179) IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't

[ https://issues.apache.org/jira/browse/CONNECTORS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13020163#comment-13020163 ] Karl Wright commented on CONNECTORS-179: Also r1092568. IConnector

[jira] [Created] (CONNECTORS-180) Connector factories all have a Pool class that should be derived from a base Pool class

Project: ManifoldCF Issue Type: Improvement Components: Framework core Reporter: Karl Wright Priority: Minor There's a fair bit of duplicated code in the connector factories - RepositoryConnectorFactory, AuthorityConnectorFactory, etc

[jira] [Created] (CONNECTORS-181) ICacheDescription's way of handling object expiration is very clumsy for fixed lifetime objects

/CONNECTORS-181 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright The ICacheDescription getObjectExpirationTime() method works fine for the model

[jira] [Resolved] (CONNECTORS-182) Timed cache invalidation does not work

[ https://issues.apache.org/jira/browse/CONNECTORS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-182. Resolution: Fixed Fix Version/s: ManifoldCF next r1094053. Timed cache

[jira] [Resolved] (CONNECTORS-32) A general access-token cache within Authority Service would help performance

[ https://issues.apache.org/jira/browse/CONNECTORS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-32. --- Resolution: Fixed Fix Version/s: ManifoldCF next r1094217. A general access

[jira] [Assigned] (CONNECTORS-183) SECURITY_AUTHENTICATION-changeable

[ https://issues.apache.org/jira/browse/CONNECTORS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-183: -- Assignee: Karl Wright SECURITY_AUTHENTICATION-changeable

[jira] [Created] (CONNECTORS-187) WorkerThread method processDeleteList does not handle ServiceInterruptions from output connector optimally

://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 next Reporter: Karl Wright The processDeleteList method in WorkerThread does

[jira] [Assigned] (CONNECTORS-188) CRLF line endings in executecommand.sh script

[ https://issues.apache.org/jira/browse/CONNECTORS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-188: -- Assignee: Karl Wright CRLF line endings in executecommand.sh script

[jira] [Resolved] (CONNECTORS-188) CRLF line endings in executecommand.sh script

[ https://issues.apache.org/jira/browse/CONNECTORS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-188. Resolution: Fixed Fix Version/s: ManifoldCF next r1096922 (trunk) r1096925

[jira] [Commented] (CONNECTORS-189) Add the mail archive links to the mail.html page

[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13025533#comment-13025533 ] Karl Wright commented on CONNECTORS-189: Do you want to contribute a patch

[jira] [Commented] (CONNECTORS-189) Add the mail archive links to the mail.html page

[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13025542#comment-13025542 ] Karl Wright commented on CONNECTORS-189: That looks about right. But you'll

[jira] [Updated] (CONNECTORS-189) Add the mail archive links to the mail.html page

[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-189: --- Resolution: Fixed Fix Version/s: (was: ManifoldCF 0.2

[jira] [Created] (CONNECTORS-190) Programmatic operation page has a wiki link in a Forrest page

Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Priority: Minor The following wiki markup is present in the programmatic-operation.xml page: [here|http://www.json.org] This should be an a href

[jira] [Resolved] (CONNECTORS-190) Programmatic operation page has a wiki link in a Forrest page

[ https://issues.apache.org/jira/browse/CONNECTORS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-190. Resolution: Fixed Assignee: Karl Wright r1097192. Programmatic operation page

[jira] [Commented] (CONNECTORS-189) Add the mail archive links to the mail.html page

[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026154#comment-13026154 ] Karl Wright commented on CONNECTORS-189: Please! What did you have in mind

[jira] [Created] (CONNECTORS-191) All .bat files should have CRLF attribute in svn

: Documentum connector, FileNet connector, Framework agents process Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Priority: Minor All .bat files should have svn:eol-style CRLF in svn, so they always

[jira] [Resolved] (CONNECTORS-191) All .bat files should have CRLF attribute in svn

[ https://issues.apache.org/jira/browse/CONNECTORS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-191. Resolution: Fixed Fix Version/s: ManifoldCF next r1097349 All .bat files

[jira] [Created] (CONNECTORS-192) Job-related specification post method sometimes called without corresponding specification header/body

/browse/CONNECTORS-192 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright For specification tabs, sometimes

[jira] [Created] (CONNECTORS-193) Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods

: https://issues.apache.org/jira/browse/CONNECTORS-193 Project: ManifoldCF Issue Type: Bug Components: GTS connector, Lucene/SOLR connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright The convention for form

[jira] [Created] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots

Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc

[jira] [Created] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly

Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which

[jira] [Updated] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly

[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-195: --- Attachment: CONNECTORS-195.patch Patch which may work to resolve the issue Active

[jira] [Commented] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly

[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028090#comment-13028090 ] Karl Wright commented on CONNECTORS-195: The patch requires the name

[jira] [Commented] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly

[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028091#comment-13028091 ] Karl Wright commented on CONNECTORS-195: The following reference is very

[jira] [Commented] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots

[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028282#comment-13028282 ] Karl Wright commented on CONNECTORS-194: cli-xconf seems definitely the way

[jira] [Issue Comment Edited] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots

[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028282#comment-13028282 ] Karl Wright edited comment on CONNECTORS-194 at 5/3/11 4:08 PM

[jira] [Assigned] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly

[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-195: -- Assignee: Karl Wright Active directory authority doesn't handle unknown user case

[jira] [Resolved] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly

[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-195. Resolution: Fixed Fix Version/s: ManifoldCF next Verified that the committed

[jira] [Resolved] (CONNECTORS-196) Active directory authority doesn't work if login name and common name differ

[ https://issues.apache.org/jira/browse/CONNECTORS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-196. Resolution: Fixed Fix Version/s: ManifoldCF next r1100090 Active directory

[jira] [Created] (CONNECTORS-196) Active directory authority doesn't work if login name and common name differ

: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Active directory authority will not work if common name (cn) and login name

[jira] [Commented] (CONNECTORS-196) Active directory authority doesn't work if login name and common name differ

[ https://issues.apache.org/jira/browse/CONNECTORS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029779#comment-13029779 ] Karl Wright commented on CONNECTORS-196: Also, r1100097. Active directory

[jira] [Commented] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots

[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030551#comment-13030551 ] Karl Wright commented on CONNECTORS-194: Patch looks great! I'll commit

[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.

[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030568#comment-13030568 ] Karl Wright commented on CONNECTORS-197: You might want to have a look

[jira] [Created] (CONNECTORS-198) The build.xml rat-source target complains about files in the test-output-postgres folders

Project: ManifoldCF Issue Type: Bug Affects Versions: ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright If you run ant rat-sources, you get complaints about files under various test-output-postgresql folders, which should

[jira] [Resolved] (CONNECTORS-198) The build.xml rat-source target complains about files in the test-output-postgres folders

[ https://issues.apache.org/jira/browse/CONNECTORS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-198. Resolution: Fixed Fix Version/s: ManifoldCF next r1100916. The build.xml rat

[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.

[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030669#comment-13030669 ] Karl Wright commented on CONNECTORS-197: In the patch, the following lines

[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.

[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030670#comment-13030670 ] Karl Wright commented on CONNECTORS-197: It looks like I confused Jira

[jira] [Updated] (CONNECTORS-174) The standard logging.ini file for the Quick Start should set a log format that includes at least date and time

[ https://issues.apache.org/jira/browse/CONNECTORS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-174: --- Resolution: Fixed Fix Version/s: ManifoldCF next Status: Resolved

[jira] [Resolved] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.

[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-197. Resolution: Fixed Assignee: Karl Wright r1100987. Active directory authority

[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.

[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030711#comment-13030711 ] Karl Wright commented on CONNECTORS-197: Yes, you are correct. The only thing

[jira] [Created] (CONNECTORS-199) Modify site release page to include new release

: Documentation Affects Versions: ManifoldCF next Reporter: Karl Wright The site release page needs to be modified, so that the site points to the new release (0.2-incubating). Also, the PostgreSQL caveat only applies to the 0.1-incubating release, and will not to the 0.2-incubating

[jira] [Created] (CONNECTORS-200) Solr connector should treat TikaException the same as a 400 response

Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Solr connector should treat TikaException the same as a 400 response, which is to skip

[jira] [Commented] (CONNECTORS-200) Solr connector should treat TikaException the same as a 400 response

[ https://issues.apache.org/jira/browse/CONNECTORS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036166#comment-13036166 ] Karl Wright commented on CONNECTORS-200: r1124712 is a trial fix. Solr

[jira] [Resolved] (CONNECTORS-200) Solr connector should treat TikaException the same as a 400 response

[ https://issues.apache.org/jira/browse/CONNECTORS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-200. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1125333 Solr connector

[jira] [Created] (CONNECTORS-201) Carrydown methods should have their own interface class

Components: Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor The carrydown methods are shared in IVersionActivity and IProcessActivity. They ought to have their own interface. -- This message is automatically

[jira] [Resolved] (CONNECTORS-201) Carrydown methods should have their own interface class

[ https://issues.apache.org/jira/browse/CONNECTORS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-201. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1126427 Carrydown methods

[jira] [Commented] (CONNECTORS-19) Look into converting SOLR connector to use SolrJ java library

[ https://issues.apache.org/jira/browse/CONNECTORS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038360#comment-13038360 ] Karl Wright commented on CONNECTORS-19: --- The promised patch never materialized

[jira] [Commented] (CONNECTORS-19) Look into converting SOLR connector to use SolrJ java library

[ https://issues.apache.org/jira/browse/CONNECTORS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038521#comment-13038521 ] Karl Wright commented on CONNECTORS-19: --- That's why this ticket was created

[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin

[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038658#comment-13038658 ] Karl Wright commented on CONNECTORS-202: Yes, making it explicit is preferred

[jira] [Commented] (CONNECTORS-203) Consider porting ManifoldCF to Java 1.5 code standards

[ https://issues.apache.org/jira/browse/CONNECTORS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041503#comment-13041503 ] Karl Wright commented on CONNECTORS-203: I've created a branch (branches

[jira] [Commented] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby

[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042655#comment-13042655 ] Karl Wright commented on CONNECTORS-110: HSQLDB is now also in roughly

[jira] [Updated] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB

[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-110: --- Summary: Max activity and Max bandwidth reports don't work properly under Derby

[jira] [Created] (CONNECTORS-204) Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it

Project: ManifoldCF Issue Type: Improvement Components: Build Reporter: Karl Wright The latest HSQLDB fixes and features make it an attractive alternative to Derby. But we need a test target that exercises it. -- This message is automatically generated by JIRA

[jira] [Commented] (CONNECTORS-203) Consider porting ManifoldCF to Java 1.5 code standards

[ https://issues.apache.org/jira/browse/CONNECTORS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042724#comment-13042724 ] Karl Wright commented on CONNECTORS-203: I've merged in all the major

[jira] [Created] (CONNECTORS-205) Database DISTINCT ON abstraction needs to include ordering information in order to work for HSQLDB

/CONNECTORS-205 Project: ManifoldCF Issue Type: Bug Components: Framework core, Framework crawler agent Reporter: Karl Wright The constructDistinctOnClause database method cannot support HSQLDB because it presumes that the ORDER BY clause is already part

[jira] [Commented] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB

[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042861#comment-13042861 ] Karl Wright commented on CONNECTORS-110: r1130644 implements this for HSQLDB

[jira] [Commented] (CONNECTORS-114) Derby seems too unstable in multithreaded situations to be a good database for ManifoldCF, so try to add support for HSQLDB

[ https://issues.apache.org/jira/browse/CONNECTORS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043369#comment-13043369 ] Karl Wright commented on CONNECTORS-114: Remaining issues with HSQLDB have

[jira] [Resolved] (CONNECTORS-114) Derby seems too unstable in multithreaded situations to be a good database for ManifoldCF, so try to add support for HSQLDB

[ https://issues.apache.org/jira/browse/CONNECTORS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-114. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright

[jira] [Updated] (CONNECTORS-206) HSQLDB is now a first-class ManifoldCF database; we should describe how to use it in the documentation

[ https://issues.apache.org/jira/browse/CONNECTORS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-206: --- Affects Version/s: ManifoldCF 0.3 HSQLDB is now a first-class ManifoldCF database; we

[jira] [Created] (CONNECTORS-207) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-second retry, but should probably abort the job instead

URL: https://issues.apache.org/jira/browse/CONNECTORS-207 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3 Reporter: Karl Wright The way a worker thread

[jira] [Updated] (CONNECTORS-207) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead

[ https://issues.apache.org/jira/browse/CONNECTORS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-207: --- Description: The way a worker thread treats ManifoldCFException type

[jira] [Commented] (CONNECTORS-204) Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it

[ https://issues.apache.org/jira/browse/CONNECTORS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044007#comment-13044007 ] Karl Wright commented on CONNECTORS-204: r1131177 has part of the code. Now

<    3   4   5   6   7   8   9   10   11   12   >