Next release?
A lot of fairly critical fixes and changes have already taken place since ManifoldCF 0.1 went out. When do you think we should try to release ManifoldCF 0.2? Or, do you think a 0.1.1 release would be the right approach? Karl
[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 connectors that have their own class loaders, we need to provide a > way of creating derivative resource loaders > - > > Key: CONNECTORS-162 > 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 > Fix For: ManifoldCF next > > > ManifoldCF currently creates its own resource loader, which adds jars to the > class path based on properties.xml parameters. Connectors may need to create > derivative resource loaders, to isolate conflicting jars, and we should make > this easy. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONNECTORS-162) To support connectors that have their own class loaders, we need to provide a way of creating derivative resource loaders
To support connectors that have their own class loaders, we need to provide a way of creating derivative resource loaders - Key: CONNECTORS-162 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 its own resource loader, which adds jars to the class path based on properties.xml parameters. Connectors may need to create derivative resource loaders, to isolate conflicting jars, and we should make this easy. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONNECTORS-161) API REST problem mcf-api-service/jobstatuses/
[ https://issues.apache.org/jira/browse/CONNECTORS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997185#comment-12997185 ] Karl Wright commented on CONNECTORS-161: This was fix on trunk a little while ago. If you want, I can generate a patch for the release. The fixed ticket was CONNECTORS-155. > API REST problem mcf-api-service/jobstatuses/ > - > > Key: CONNECTORS-161 > URL: https://issues.apache.org/jira/browse/CONNECTORS-161 > Project: ManifoldCF > Issue Type: New Feature > Components: Framework core >Affects Versions: ManifoldCF 0.1 > Environment: psql (PostgreSQL) 8.4.7 >Reporter: Nicolas Max > Labels: postgres > > ~/mcf-api-service/json/jobstatuses/ > Not work with PostgreSQL. The error is : > {"error":"Database exception: Exception doing query: ERROR: operator does not > exist: bigint = character varying"} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (CONNECTORS-161) API REST problem mcf-api-service/jobstatuses/
[ https://issues.apache.org/jira/browse/CONNECTORS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-161. Resolution: Duplicate Duplicate of CONNECTORS-155. > API REST problem mcf-api-service/jobstatuses/ > - > > Key: CONNECTORS-161 > URL: https://issues.apache.org/jira/browse/CONNECTORS-161 > Project: ManifoldCF > Issue Type: New Feature > Components: Framework core >Affects Versions: ManifoldCF 0.1 > Environment: psql (PostgreSQL) 8.4.7 >Reporter: Nicolas Max > Labels: postgres > > ~/mcf-api-service/json/jobstatuses/ > Not work with PostgreSQL. The error is : > {"error":"Database exception: Exception doing query: ERROR: operator does not > exist: bigint = character varying"} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira