[jira] [Assigned] (CONNECTORS-366) Solr connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-366: -- Assignee: Karl Wright Solr connector should be fully I18N --- Key: CONNECTORS-366 URL: https://issues.apache.org/jira/browse/CONNECTORS-366 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-366.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] [Assigned] (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 reassigned CONNECTORS-367: -- Assignee: Karl Wright 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] [Assigned] (CONNECTORS-368) Wiki connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-368: -- Assignee: Karl Wright Wiki connector should be fully I18N --- Key: CONNECTORS-368 URL: https://issues.apache.org/jira/browse/CONNECTORS-368 Project: ManifoldCF Issue Type: Improvement Components: Wiki connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-368.patch All messages should be extracted 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] [Commented] (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:comment-tabpanelfocusedCommentId=13182562#comment-13182562 ] Karl Wright commented on CONNECTORS-359: r1229217. 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] [Commented] (CONNECTORS-358) All messages in Filenet connector should be extracted out to properties file and Japanese messages added
[ https://issues.apache.org/jira/browse/CONNECTORS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182563#comment-13182563 ] Karl Wright commented on CONNECTORS-358: r1229215 All messages in Filenet connector should be extracted out to properties file and Japanese messages added Key: CONNECTORS-358 URL: https://issues.apache.org/jira/browse/CONNECTORS-358 Project: ManifoldCF Issue Type: Improvement Components: FileNet connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-358.patch All messages in Filenet connector should be extracted out to properties file and Japanese messages added to fully support I18N and Japanese L10N. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-360) GTS connector should be I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182576#comment-13182576 ] Karl Wright commented on CONNECTORS-360: r1229223 GTS connector should be I18N Key: CONNECTORS-360 URL: https://issues.apache.org/jira/browse/CONNECTORS-360 Project: ManifoldCF Issue Type: Improvement Components: GTS connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-360.patch Should extract out all messages in GTS connector to support I18N 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] [Commented] (CONNECTORS-365) Sharepoint connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182589#comment-13182589 ] Karl Wright commented on CONNECTORS-365: r1229230 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] [Commented] (CONNECTORS-367) WebCrawler connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182590#comment-13182590 ] Karl Wright commented on CONNECTORS-367: r1229231 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] [Commented] (CONNECTORS-368) Wiki connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182593#comment-13182593 ] Karl Wright commented on CONNECTORS-368: r1229234 Wiki connector should be fully I18N --- Key: CONNECTORS-368 URL: https://issues.apache.org/jira/browse/CONNECTORS-368 Project: ManifoldCF Issue Type: Improvement Components: Wiki connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-368.patch All messages should be extracted 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-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] [Commented] (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:comment-tabpanelfocusedCommentId=13182700#comment-13182700 ] Karl Wright commented on CONNECTORS-357: r1229289 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] [Commented] (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:comment-tabpanelfocusedCommentId=13182723#comment-13182723 ] Karl Wright commented on CONNECTORS-359: r1229305 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-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] [Commented] (CONNECTORS-360) GTS connector should be I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182730#comment-13182730 ] Karl Wright commented on CONNECTORS-360: r1229317 GTS connector should be I18N Key: CONNECTORS-360 URL: https://issues.apache.org/jira/browse/CONNECTORS-360 Project: ManifoldCF Issue Type: Improvement Components: GTS connector Affects Versions: ManifoldCF 0.5 Reporter: Hitoshi Ozawa Assignee: Karl Wright Priority: Minor Labels: I18N Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-360.patch Should extract out all messages in GTS connector to support I18N 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-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] [Commented] (CONNECTORS-363) LiveLink connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182762#comment-13182762 ] Karl Wright commented on CONNECTORS-363: r1229336 The messages in the LivelinkAuthority.java look like they've been updated, but the ones in LivelinkConnector.java have not. 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 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] [Commented] (CONNECTORS-364) RSS Connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182861#comment-13182861 ] Karl Wright commented on CONNECTORS-364: r1229393 RSS Connector should be fully I18N -- Key: CONNECTORS-364 URL: https://issues.apache.org/jira/browse/CONNECTORS-364 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-364.patch All messages in RSS 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] [Commented] (CONNECTORS-367) WebCrawler connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182865#comment-13182865 ] Karl Wright commented on CONNECTORS-367: r1229398 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-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] [Commented] (CONNECTORS-365) Sharepoint connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182901#comment-13182901 ] Karl Wright commented on CONNECTORS-365: r1229410 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-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] [Assigned] (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 reassigned CONNECTORS-370:
--
Assignee: Karl Wright
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] [Commented] (CONNECTORS-370) Ability to pass parameters to I18N messages
[
https://issues.apache.org/jira/browse/CONNECTORS-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182909#comment-13182909
]
Karl Wright commented on CONNECTORS-370:
There's already code in the Messages class for optional arguments, which do
this:
{code}
// Format the message
String formatMessage;
if (args != null)
{
formatMessage = MessageFormat.format(message, args);
}
else
{
formatMessage = message;
}
return formatMessage;
{code}
For example:
{code}
Object[] testArgs = {new Long(3), MyDisk};
MessageFormat form = new MessageFormat(
The disk \{1}\ contains {0} file(s).);
System.out.println(form.format(testArgs));
// output, with different testArgs
output: The disk MyDisk contains 0 file(s).
output: The disk MyDisk contains 1 file(s).
output: The disk MyDisk contains 1,273 file(s).
{code}
The problem with MessageFormat is that it seems to use the current default
locale exclusively when formatting the arguments. As long as the arguments are
strings this isn't a problem, but if any turn out to be numbers etc then
MessageFormat will not do the right thing.
My suggestion is thus to (a) keep the general functionality of MessageFormat,
but (b) reimplement the parts we use so that it uses the right locale.
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] [Commented] (CONNECTORS-370) Ability to pass parameters to I18N messages
[
https://issues.apache.org/jira/browse/CONNECTORS-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182913#comment-13182913
]
Karl Wright commented on CONNECTORS-370:
r1229416 corrects the locale issue (I think)...
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-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] [Commented] (CONNECTORS-356) Active Directory connector should by fully I18N/L10N
[
https://issues.apache.org/jira/browse/CONNECTORS-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182917#comment-13182917
]
Karl Wright commented on CONNECTORS-356:
bq. I thought you wanted a separate issue for each connector.
Separate issue, separate patch, but patch should be created so that it can be
applied from the trunk directory, not somewhere deep in the hierarchy. You can
create such a diff like this:
{code}
cd ~/mcf/trunk
svn diff connectors/xyz CONNECTORS-123.patch
{code}
Active Directory connector should by fully I18N/L10N
Key: CONNECTORS-356
URL: https://issues.apache.org/jira/browse/CONNECTORS-356
Project: ManifoldCF
Issue Type: Improvement
Components: Active Directory authority
Affects Versions: ManifoldCF 0.5
Reporter: Hitoshi Ozawa
Assignee: Karl Wright
Priority: Minor
Labels: I18N
Fix For: ManifoldCF 0.5
Attachments: CONNECTORS-356.patch
All messages in Active Directory Connector should be extracted out to
properties file.
Also, should create Japanese L10N properties file for all messages.
--
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] [Commented] (CONNECTORS-345) Jetty Configuration Support
[ https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182180#comment-13182180 ] Karl Wright commented on CONNECTORS-345: Any news on this? Did ManifoldCF work with jetty 7? Jetty Configuration Support --- Key: CONNECTORS-345 URL: https://issues.apache.org/jira/browse/CONNECTORS-345 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.4 Environment: Jetty Configuration Reporter: Michael J. Kelleher Assignee: Karl Wright Fix For: ManifoldCF 0.5 Can the single process example be extended to support Jetty configuration? 1) jetty.xml 2) webdefault.xml 3) OPTIONS= along with their corresponding XML config files, most importantly the JMX option, Server,ajp,setuid would be nice to have -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13181387#comment-13181387 ] Karl Wright commented on CONNECTORS-336: bq. I may have messed up my svn on Ubuntu by copying files I've edited on my Windows7 Copying files shouldn't mess up svn, but copying workspaces/hidden files certainly could. If you're not sure it may be best to create a new workspace at this point. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336-20120106.patch, CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, CONNECTORS-336_20120105.patch, ja_JP_A.zip, ja_JP_B.zip, ja_JP_C.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13181387#comment-13181387 ] Karl Wright edited comment on CONNECTORS-336 at 1/6/12 3:26 PM: bq. I may have messed up my svn on Ubuntu by copying files I've edited on my Windows7 Copying files shouldn't mess up svn, but copying workspaces/hidden files certainly could. If you're not sure it may be best to create a new workspace at this point. Once you do that, you should notice that there's no ja_JP/index*.xml file. Then you can add yours back and do an svn diff to get the next patch. was (Author: kwri...@metacarta.com): bq. I may have messed up my svn on Ubuntu by copying files I've edited on my Windows7 Copying files shouldn't mess up svn, but copying workspaces/hidden files certainly could. If you're not sure it may be best to create a new workspace at this point. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336-20120106.patch, CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, CONNECTORS-336_20120105.patch, ja_JP_A.zip, ja_JP_B.zip, ja_JP_C.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13180356#comment-13180356 ] Karl Wright commented on CONNECTORS-336: The new patch fails on tab.xml and site.xml: patching file xdocs/tabs.xml Reversed (or previously applied) patch detected! Assume -R? [n] y patching file xdocs/site.xml Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #2 FAILED at 75. 1 out of 2 hunks FAILED -- saving rejects to file xdocs/site.xml.rej Are you sure you did an svn diff against the current contents of the branch? If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, CONNECTORS-336_20120105.patch, ja_JP_A.zip, ja_JP_B.zip, ja_JP_C.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13180356#comment-13180356 ] Karl Wright edited comment on CONNECTORS-336 at 1/5/12 1:20 PM: The new patch fails on tab.xml and site.xml: patching file xdocs/tabs.xml Reversed (or previously applied) patch detected! Assume -R? [n] y patching file xdocs/site.xml Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #2 FAILED at 75. 1 out of 2 hunks FAILED -- saving rejects to file xdocs/site.xml.rej Are you sure you did an svn diff against the current contents of the branch? Try svn update before you do the svn diff. was (Author: kwri...@metacarta.com): The new patch fails on tab.xml and site.xml: patching file xdocs/tabs.xml Reversed (or previously applied) patch detected! Assume -R? [n] y patching file xdocs/site.xml Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #2 FAILED at 75. 1 out of 2 hunks FAILED -- saving rejects to file xdocs/site.xml.rej Are you sure you did an svn diff against the current contents of the branch? If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, CONNECTORS-336_20120105.patch, ja_JP_A.zip, ja_JP_B.zip, ja_JP_C.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13180374#comment-13180374 ] Karl Wright commented on CONNECTORS-336: I committed the changes indicated to the PNG's; that worked and made sense. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, CONNECTORS-336_20120105.patch, ja_JP_A.zip, ja_JP_B.zip, ja_JP_C.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-286) Get ManifoldCF to run on top of a key/value store like Voldemort, for potential massive scalability improvements and speed gains
[ https://issues.apache.org/jira/browse/CONNECTORS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13181155#comment-13181155 ] Karl Wright commented on CONNECTORS-286: bq. Not sure what Wharthog is... See https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-286/warthog. Warthog is a potential future spinoff technology of ManifoldCF - if all this stuff actually works. ;-) bq. But I wanted to suggest you consider using HBase for underlying storage. Maybe. One of the apparent requirements of ManifoldCF is the ability run on top of practically anything. I don't think we'd be able to throw away PostgreSQL and MySQL and HSQLDB and Derby support for instance. So if Warthog is the actual API layer ManifoldCF uses then we'd need implementations of Warthog for as many backends as possible. Right now I've only going one for a testing key-value store, but almost certainly the next step would be a SQL database. Then moving on from then HBase (or Hive/Pig) may also be possibilities. Still proving the concept however... Get ManifoldCF to run on top of a key/value store like Voldemort, for potential massive scalability improvements and speed gains Key: CONNECTORS-286 URL: https://issues.apache.org/jira/browse/CONNECTORS-286 Project: ManifoldCF Issue Type: New Feature Components: Framework core Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next ManifoldCF's reliance on a relational database limits its throughput and scalability. I am now convinced it is possible to build all the structures we need within a distributed key-value store like Voldemort, which has the nice side effect of permitting massive scaling. I envision there will be several layers to this project, some of which may have broader utility in the open-source community at large: (1) An atomic serialization layer, which adds serialization capabilities to an non-transactional substrate; (2) A transaction layer, which uses atomic serialization to build a notion of light transactions; (3) A table and index layer, which defines SQL-like concepts of tables and btree indexes on top of the transaction layer, via a Java API; (4) A generic database abstraction layer, which is capable of representing both standard SQL databases as well as this NoSQL variant, so that ManifoldCF can support both models. This is obviously a major development task, and as such is not envisioned to be completed by the next standard release. Work will indeed need to be done in a branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-286) Get ManifoldCF to run on top of a key/value store like Voldemort, for potential massive scalability improvements and speed gains
[ https://issues.apache.org/jira/browse/CONNECTORS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13181155#comment-13181155 ] Karl Wright edited comment on CONNECTORS-286 at 1/6/12 6:23 AM: bq. Not sure what Wharthog is... See https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-286/warthog. Warthog is a potential future spinoff technology of ManifoldCF - if all this stuff actually works. ;-) bq. But I wanted to suggest you consider using HBase for underlying storage. Maybe. One of the apparent requirements of ManifoldCF is the ability run on top of practically anything. I don't think we'd be able to throw away PostgreSQL and MySQL and HSQLDB and Derby support for instance. So if Warthog is the actual API layer ManifoldCF uses then we'd need implementations of Warthog for as many backends as possible. Right now I've only got one going for a testing key-value store, but almost certainly the next step would be a SQL database. Then moving on from then HBase (or Hive/Pig) may also be possibilities. Still proving the concept however... was (Author: kwri...@metacarta.com): bq. Not sure what Wharthog is... See https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-286/warthog. Warthog is a potential future spinoff technology of ManifoldCF - if all this stuff actually works. ;-) bq. But I wanted to suggest you consider using HBase for underlying storage. Maybe. One of the apparent requirements of ManifoldCF is the ability run on top of practically anything. I don't think we'd be able to throw away PostgreSQL and MySQL and HSQLDB and Derby support for instance. So if Warthog is the actual API layer ManifoldCF uses then we'd need implementations of Warthog for as many backends as possible. Right now I've only going one for a testing key-value store, but almost certainly the next step would be a SQL database. Then moving on from then HBase (or Hive/Pig) may also be possibilities. Still proving the concept however... Get ManifoldCF to run on top of a key/value store like Voldemort, for potential massive scalability improvements and speed gains Key: CONNECTORS-286 URL: https://issues.apache.org/jira/browse/CONNECTORS-286 Project: ManifoldCF Issue Type: New Feature Components: Framework core Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next ManifoldCF's reliance on a relational database limits its throughput and scalability. I am now convinced it is possible to build all the structures we need within a distributed key-value store like Voldemort, which has the nice side effect of permitting massive scaling. I envision there will be several layers to this project, some of which may have broader utility in the open-source community at large: (1) An atomic serialization layer, which adds serialization capabilities to an non-transactional substrate; (2) A transaction layer, which uses atomic serialization to build a notion of light transactions; (3) A table and index layer, which defines SQL-like concepts of tables and btree indexes on top of the transaction layer, via a Java API; (4) A generic database abstraction layer, which is capable of representing both standard SQL databases as well as this NoSQL variant, so that ManifoldCF can support both models. This is obviously a major development task, and as such is not envisioned to be completed by the next standard release. Work will indeed need to be done in a branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179407#comment-13179407 ] Karl Wright commented on CONNECTORS-336: bq. How do I upload PNG files? Just attach them as a .zip or .tar.gz If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179416#comment-13179416 ] Karl Wright commented on CONNECTORS-336: I committed the B patch to the CONNECTORS-336 branch. r1227119. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179418#comment-13179418 ] Karl Wright commented on CONNECTORS-336: The A patch will not commit; it's just properties and is interpreted as garbage by the patch utility. Attach a .zip instead of the PNGs and I'll be happy to commit those. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179461#comment-13179461 ] Karl Wright commented on CONNECTORS-336: bq. I can't attach a zip here. It seems to hangup every time I try. How large is the zip? If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179461#comment-13179461 ] Karl Wright edited comment on CONNECTORS-336 at 1/4/12 1:18 PM: bq. I can't attach a zip here. It seems to hangup every time I try. How large is the zip? I believe the limit is 10mb (or maybe even 5mb), so if it's bigger than that you'll need to break it up into pieces. was (Author: kwri...@metacarta.com): bq. I can't attach a zip here. It seems to hangup every time I try. How large is the zip? If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- 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
[RESULT][VOTE] Release apache-manifoldcf-0.4-incubating, RC2
Three days, three +1's. Vote passes! Now all we need is for our mentors to vote in general@i.a.o. Karl On Tue, Jan 3, 2012 at 7:26 AM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: +1 - Checked md5 and sha1 sums for all packages - Downladed apache-manifoldcf-0.4-incubating-src.tar.gz on OSX and built it - Generated docs and javadocs and verified the content - Ran ant test - Ran the Jetty example application and tried the web crawler and posted to Solr 3.1 - Installed the war files on Resin/Linux and started a huge crawl and posted to Solr This looks very good. Erlend On 01.01.12 22.35, Karl Wright wrote: This release candidate has another fix for the Alfresco connector for a problem which prevented it from loading binary data into the search index. Please vote +1 to release RC2. You can find the artifact in the usual place, http://people.apache.org/~kwright/apache-manifoldcf-0.4-incubating. Thanks, Karl -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179920#comment-13179920 ] Karl Wright commented on CONNECTORS-336: bq. The zip file I want to attach is about 8MB so it's under 10mb. Other people have uploaded zips to Jira successfully. Can you break it up into two roughly equal pieces and try that? 5Mb may be the limit. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179920#comment-13179920 ] Karl Wright edited comment on CONNECTORS-336 at 1/4/12 10:02 PM: - bq. The zip file I want to attach is about 8MB so it's under 10mb. Other people have uploaded zips to Jira successfully. Can you break it up into two roughly equal pieces and try that? 5Mb may be the limit. If that doesn't work just email the zip to me at daddy...@gmail.com, and I'll check it in. was (Author: kwri...@metacarta.com): bq. The zip file I want to attach is about 8MB so it's under 10mb. Other people have uploaded zips to Jira successfully. Can you break it up into two roughly equal pieces and try that? 5Mb may be the limit. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13180037#comment-13180037 ] Karl Wright commented on CONNECTORS-336: r1227412 to commit the images, hopefully in the intended place. I haven't yet tried to build. A couple of comments: (1) It's probably unnecessary to duplicate logos and icons; I think we should just leave these in the root images directory. (2) Same comment about.gifs used by the Forrest skin we're using. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, ja_JP_A.zip, ja_JP_B.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-336) If there's a Japanese localization, we should also have some Japanese documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13180078#comment-13180078 ] Karl Wright commented on CONNECTORS-336: Tried to build it, but index_ja_JP.xml is not valid utf-8. Furthermore, it appears twice: once in site/src/documentation/content/xdocs, and once in site/src/documentation/content/xdocs/ja_JP. All the other .xml files look like valid utf-8. If there's a Japanese localization, we should also have some Japanese documentation --- Key: CONNECTORS-336 URL: https://issues.apache.org/jira/browse/CONNECTORS-336 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-336_20120104A.patch, CONNECTORS-336_20120104B.patch, ja_JP_A.zip, ja_JP_B.zip We should provide some Japanese documentation if we have a Japanese localization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-286) Get ManifoldCF to run on top of a key/value store like Voldemort, for potential massive scalability improvements and speed gains
[ https://issues.apache.org/jira/browse/CONNECTORS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178695#comment-13178695 ] Karl Wright commented on CONNECTORS-286: Using the Warthog API as the standard ManifoldCF way of dealing with databases may not be practical, for the following reasons. - A significant amount of the actual functionality of Warthog comes from java methods you supply to it. This is incompatible fundamentally with using a standard database to do the same thing, because there are bound to be situations where the two implementations disagree. - A full database implementation under Warthog entails using the database for table storage and index access (ordered) with conditions applied to the index. Warthog would do the rest. But it is conceivable that this would not perform as well as native database queries. - It is not clear how to construct a cache key in Warthog, so caching database results will require some thought. Caching at the interface to the underlying database is not practical at all, because only partial resultsets will be read from many of the queries. - It's not even clear (yet) whether critical functionality is missing from Warthog that will be needed to implement ManifoldCF. Nevertheless, the next step is to try to create an implementation of Warthog where WHTableStore, WHTable, and WHIndex are implemented by an underlying relational database. The difficulty in this, as stated above, occurs because the index (for example) is defined in terms of a WHComparator for each column being indexed, which is opaque Java code. Instead of merely performing the comparison, the code must, in addition, be in accordance with what the database is doing, AND also be capable of assisting in the generation of SQL code. Special SQL-consistent WHComparator implementations are therefore going to be necessary, which also implement another interface (SQLInspectable?). The WHIndex implementation can therefore use them to do what it needs, and complain if somebody tries to use incompatible comparator implementations. Thus, each implementation of the Warthog API consists of: - Implementations of WHTableStore and WHTable and WHIndex - A body of comparators, filters, etc. that implement data types consistent with the SQL database Get ManifoldCF to run on top of a key/value store like Voldemort, for potential massive scalability improvements and speed gains Key: CONNECTORS-286 URL: https://issues.apache.org/jira/browse/CONNECTORS-286 Project: ManifoldCF Issue Type: New Feature Components: Framework core Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next ManifoldCF's reliance on a relational database limits its throughput and scalability. I am now convinced it is possible to build all the structures we need within a distributed key-value store like Voldemort, which has the nice side effect of permitting massive scaling. I envision there will be several layers to this project, some of which may have broader utility in the open-source community at large: (1) An atomic serialization layer, which adds serialization capabilities to an non-transactional substrate; (2) A transaction layer, which uses atomic serialization to build a notion of light transactions; (3) A table and index layer, which defines SQL-like concepts of tables and btree indexes on top of the transaction layer, via a Java API; (4) A generic database abstraction layer, which is capable of representing both standard SQL databases as well as this NoSQL variant, so that ManifoldCF can support both models. This is obviously a major development task, and as such is not envisioned to be completed by the next standard release. Work will indeed need to be done in a branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-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 updated CONNECTORS-258: --- Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.3 Assignee: Karl Wright 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-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] [Updated] (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 updated CONNECTORS-318:
---
Affects Version/s: ManifoldCF 0.5
Fix Version/s: ManifoldCF 0.5
Assignee: Karl Wright
Although it's far better to have the Solr connector handle its own diagnostics,
this patch may still be helpful upon occasion, so I recommend committing it.
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] [Updated] (CONNECTORS-309) On Canonicalization Tab , Allow regex transforms to modify the URL's for a crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-309: --- Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.5 Assignee: Karl Wright As stated this looks straightforward and will probably fit in the 0.5 timeframe. On Canonicalization Tab , Allow regex transforms to modify the URL's for a crawl Key: CONNECTORS-309 URL: https://issues.apache.org/jira/browse/CONNECTORS-309 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.4 Reporter: Michael J. Kelleher Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 There was not a Component for a Job. Canonicalization is part of the Job definition. I would like the ability to use a regex to transform a URL (not necessarily including the hostname and port). Specifically what I would like to use this for is to remove certain URL request parameters from the URL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-292) Problems compiling agents, pull-agent, connectors/filesystem, etc directly in Maven
[
https://issues.apache.org/jira/browse/CONNECTORS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179064#comment-13179064
]
Karl Wright commented on CONNECTORS-292:
Given the open-endedness of this ticket, I'm going to triage it into
ManifoldCF-next.
Problems compiling agents, pull-agent, connectors/filesystem, etc directly in
Maven
---
Key: CONNECTORS-292
URL: https://issues.apache.org/jira/browse/CONNECTORS-292
Project: ManifoldCF
Issue Type: Bug
Components: Build
Affects Versions: ManifoldCF 0.4
Environment: java 6, maven 3.0.3, ManifoldCF trunk version from
http://svn.apache.org/repos/asf/incubator/lcf/trunk
Reporter: Luca Stancapiano
Priority: Minor
Fix For: ManifoldCF next
if I try to execute the command 'mvn install -Dmaven.test.skip inside
'framework/agents' I get this error:
[ERROR] Failed to execute goal on project mcf-agents: Could not resolve
dependencies for project org.apache.manifoldcf:mcf-agents:jar:0.4.0-SNAPSHOT:
Failure to find org.apache.manifoldcf:mcf-core:jar:tests:0.4.0-SNAPSHOT in
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]
In the pom.xml of the mcf-agents project there is a wrong dependency:
dependency
groupId${project.groupId}/groupId
artifactIdmcf-core/artifactId
version${project.version}/version
typetest-jar/type
scopetest/scope
/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] [Updated] (CONNECTORS-351) Alfresco Connector documentation must be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-351: --- Affects Version/s: ManifoldCF 0.5 Fix Version/s: ManifoldCF 0.5 Alfresco Connector documentation must be updated Key: CONNECTORS-351 URL: https://issues.apache.org/jira/browse/CONNECTORS-351 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.5 Original Estimate: 2h Remaining Estimate: 2h The Alfresco connector documentation must be updated with the new tenant domain parameter (text and screenshots). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-345) Jetty Configuration Support
[ https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-345: --- Fix Version/s: ManifoldCF 0.5 Assignee: Karl Wright Jetty Configuration Support --- Key: CONNECTORS-345 URL: https://issues.apache.org/jira/browse/CONNECTORS-345 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.4 Environment: Jetty Configuration Reporter: Michael J. Kelleher Assignee: Karl Wright Fix For: ManifoldCF 0.5 Can the single process example be extended to support Jetty configuration? 1) jetty.xml 2) webdefault.xml 3) OPTIONS= along with their corresponding XML config files, most importantly the JMX option, Server,ajp,setuid would be nice to have -- 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
Announcing the availability of UI testing infrastructure
Folks, When ManifoldCF was granted by MetaCarta, comprehensive tests existed for the main Crawler UI as well as the UI contributions of each connector. This testing was all done in Python, and was thus unavailable within Junit, even though the MetaCarta test code itself had been granted, including the Python browser emulator (which I had written). My original plans had been to port the browser emulator to Java. I kept starting to do this but other tasks continually interfered. Eventually in December I finally gave up on having enough of a block of time to do the port, and created infrastructure instead that invokes Python directly from within the Junit test framework. So we now have limited but sufficient capability for testing connector UIs. In order to use the tester, all you have to do is the following: - Install Python 2.x on the computer you intend to test with. - Make sure that typing the command python brings up the python shell. - Execute ant uitest. Currently tests exist for the filesystem connector, the rss connector, and the web connector (which I'm currently completing). To write your own test, have a look at the code in tests/rss/src/test/java/org/apache/manifoldcf/rss_tests/NavigationDerbyUI.java. It should be pretty self-explanatory. Ask questions if it isn't. I think we should have UI tests for all connectors before we ship 0.5, so if you own a connector please consider adding such a test. Bear in mind that the UI tester is NOT going to emulate IE or Firefox, but is only capable of doing the basics. Thus, there are plenty of things you can do in Javascript in a browser that won't work in the tester. If you are trying to do something in your UI that the tester does not like, usually the best solution is to simply do it in a different way. If that can't be done, we can augment the tester as needed. Let me know if you run into this problem and I'd be happy to help. The tester is also rigorous about properly formed HTML, which is good since most browsers silently accept crappy HTML and then break things in different ways. Thanks! Karl
[jira] [Commented] (CONNECTORS-353) It would be an improvement to bundle the SharePoint and Meridio WSDD files into the connector jars as resources
[ https://issues.apache.org/jira/browse/CONNECTORS-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178407#comment-13178407 ] Karl Wright commented on CONNECTORS-353: r1226429 It would be an improvement to bundle the SharePoint and Meridio WSDD files into the connector jars as resources --- Key: CONNECTORS-353 URL: https://issues.apache.org/jira/browse/CONNECTORS-353 Project: ManifoldCF Issue Type: Improvement Components: Build, Meridio connector, SharePoint connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The wsdd axis configuration file is currently read as a file from the file system. It would be much more convenient if this could be read as a resource from within the corresponding connector jar. Unfortunately, Axis's FileProvider implementation does not really support this properly. The FileProvider(InputStream) constructor does not properly close the input stream at any point, and in any case allows it to be read only once. The ability to look through the class path is present but starts with the Axis classes (which are not in the connector jar) and also seems to leak file handles. The proper implementation therefore involves someone writing their own ResourceProvider class, implementing EngineConfiguration, with all the right characteristics. This is straightforward but obviously requires testing against a SharePoint instance before it could be committed - or, at least, confirmation the the wsdd configuration is being picked up properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-354) The Solr-3.x and Solr-4.x plugins need parameters to control size of Http connection pool
The Solr-3.x and Solr-4.x plugins need parameters to control size of Http connection pool - Key: CONNECTORS-354 URL: https://issues.apache.org/jira/browse/CONNECTORS-354 Project: ManifoldCF Issue Type: Bug Components: Solr-3.x-component, Solr-4.x-component Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Solr-3.x and 4.x plugins use an http connection pool. There needs to be a way to configure the pool size through Solr configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-354) The Solr-3.x and Solr-4.x plugins need parameters to control size of Http connection pool
[ https://issues.apache.org/jira/browse/CONNECTORS-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178414#comment-13178414 ] Karl Wright commented on CONNECTORS-354: The code that does this must be careful to do both connections per host and overall connections, e.g.: cm.getParams().setDefaultMaxConnectionsPerHost(1000); cm.getParams().setMaxTotalConnections(1000); The Solr-3.x and Solr-4.x plugins need parameters to control size of Http connection pool - Key: CONNECTORS-354 URL: https://issues.apache.org/jira/browse/CONNECTORS-354 Project: ManifoldCF Issue Type: Bug Components: Solr-3.x-component, Solr-4.x-component Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Solr-3.x and 4.x plugins use an http connection pool. There needs to be a way to configure the pool size through Solr configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-354) The Solr-3.x and Solr-4.x plugins need parameters to control size of Http connection pool
[ https://issues.apache.org/jira/browse/CONNECTORS-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178451#comment-13178451 ] Karl Wright commented on CONNECTORS-354: r1226464 for Solr-3.x plugin. r1226468 for Solr-4.x plugin. The Solr-3.x and Solr-4.x plugins need parameters to control size of Http connection pool - Key: CONNECTORS-354 URL: https://issues.apache.org/jira/browse/CONNECTORS-354 Project: ManifoldCF Issue Type: Bug Components: Solr-3.x-component, Solr-4.x-component Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Solr-3.x and 4.x plugins use an http connection pool. There needs to be a way to configure the pool size through Solr configuration. -- 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] [Commented] (CONNECTORS-344) OpenSearchServer connector needs hiddens to work in multi-tab environment
[ https://issues.apache.org/jira/browse/CONNECTORS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178204#comment-13178204 ] Karl Wright commented on CONNECTORS-344: Ok, I see some new files, but still the japanese localizations are deleted and not restored. Nevertheless, I have enough to go on and can finish the work. OpenSearchServer connector needs hiddens to work in multi-tab environment - Key: CONNECTORS-344 URL: https://issues.apache.org/jira/browse/CONNECTORS-344 Project: ManifoldCF Issue Type: Bug Components: OpenSearchServer connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: mcf-344-2.patch, mcf-344.patch The OpenSearchServer connector UI loses your data when you click on different tabs in either the output connector configuration page or job page. It needs support for hidden data in order to not do this. See other connector implementations, notably the CMIS connector (which is similar architecturally) in order to do this right. -- 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
Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC1
Do I understand it correctly that the connector as it stands in the release-0.4 branch does not actually index the binary content at all? If so I think that is serious enough to spin an RC2 for. The problem with adding a new feature at the same time is that there's a risk it will introduce yet another bug. If the feature is really straightforward and low-risk maybe we can do it, but if it is more complicated I think we'd want to check in only the fix into the release branch, and open a specific ticket for it too. Karl On Sat, Dec 31, 2011 at 3:46 PM, Piergiorgio Lucidi piergior...@apache.org wrote: Ok, we could add the support for the binary in the next release or we could add this last commit in this release. This because I committed the fix and the new improvement (Multi-Tenancy) in the same commit... DOH! So we have these two options: 1. Notify that the Alfresco connector in this release supports only metadata and add some documentation sections about this in the website. 2. Merge my last commit in the 04-incubating to add the support of binary ingestion for the Alfresco connector. Piergiorgio 2011/12/31 Karl Wright daddy...@gmail.com: This looks unrelated to the 0.4-incubating release, which does not have the alfresco multi-tenancy support at all in it. Can you clarify whether you think this is critical for the 0.4-incubating release? That is what the vote thread is for. Karl On Sat, Dec 31, 2011 at 11:32 AM, Piergiorgio Lucidi piergior...@apache.org wrote: I solved the critical issue in the main trunk (r1226128). Hope this helps. Cheers and Happy New Year! Piergiorgio 2011/12/30 Piergiorgio Lucidi piergior...@apache.org: Hi guys, I found a critical bug about the Alfresco Connector, the binary is not correctly managed [1]. I solved the issue, but I have to solve all the conflicts related to the latest changes. I hope to release soon this patch. Cheers, Piergiorgio [1] https://issues.apache.org/jira/browse/CONNECTORS-349 2011/12/29 Karl Wright daddy...@gmail.com: I've uploaded the RC1 apache-manifoldcf-0.4-incubating package which you can download from http://people.apache.org/~kwright. If you agree this should be released please vote +1. The fixes over RC0 are all UI related; you can see what they are in the CHANGES.txt file. Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com
Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC1
Nevermind about the ticket - I see that CONNECTORS-349 exists already. Can you come up with a patch against the release-0.4-incubating-branch that includes only the fix for ticket CONNECTORS-349? Karl On Sun, Jan 1, 2012 at 12:58 PM, Karl Wright daddy...@gmail.com wrote: Do I understand it correctly that the connector as it stands in the release-0.4 branch does not actually index the binary content at all? If so I think that is serious enough to spin an RC2 for. The problem with adding a new feature at the same time is that there's a risk it will introduce yet another bug. If the feature is really straightforward and low-risk maybe we can do it, but if it is more complicated I think we'd want to check in only the fix into the release branch, and open a specific ticket for it too. Karl On Sat, Dec 31, 2011 at 3:46 PM, Piergiorgio Lucidi piergior...@apache.org wrote: Ok, we could add the support for the binary in the next release or we could add this last commit in this release. This because I committed the fix and the new improvement (Multi-Tenancy) in the same commit... DOH! So we have these two options: 1. Notify that the Alfresco connector in this release supports only metadata and add some documentation sections about this in the website. 2. Merge my last commit in the 04-incubating to add the support of binary ingestion for the Alfresco connector. Piergiorgio 2011/12/31 Karl Wright daddy...@gmail.com: This looks unrelated to the 0.4-incubating release, which does not have the alfresco multi-tenancy support at all in it. Can you clarify whether you think this is critical for the 0.4-incubating release? That is what the vote thread is for. Karl On Sat, Dec 31, 2011 at 11:32 AM, Piergiorgio Lucidi piergior...@apache.org wrote: I solved the critical issue in the main trunk (r1226128). Hope this helps. Cheers and Happy New Year! Piergiorgio 2011/12/30 Piergiorgio Lucidi piergior...@apache.org: Hi guys, I found a critical bug about the Alfresco Connector, the binary is not correctly managed [1]. I solved the issue, but I have to solve all the conflicts related to the latest changes. I hope to release soon this patch. Cheers, Piergiorgio [1] https://issues.apache.org/jira/browse/CONNECTORS-349 2011/12/29 Karl Wright daddy...@gmail.com: I've uploaded the RC1 apache-manifoldcf-0.4-incubating package which you can download from http://people.apache.org/~kwright. If you agree this should be released please vote +1. The fixes over RC0 are all UI related; you can see what they are in the CHANGES.txt file. Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Commented] (CONNECTORS-344) OpenSearchServer connector needs hiddens to work in multi-tab environment
[ https://issues.apache.org/jira/browse/CONNECTORS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178215#comment-13178215 ] Karl Wright commented on CONNECTORS-344: r1226286. OpenSearchServer connector needs hiddens to work in multi-tab environment - Key: CONNECTORS-344 URL: https://issues.apache.org/jira/browse/CONNECTORS-344 Project: ManifoldCF Issue Type: Bug Components: OpenSearchServer connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: mcf-344-2.patch, mcf-344.patch The OpenSearchServer connector UI loses your data when you click on different tabs in either the output connector configuration page or job page. It needs support for hidden data in order to not do this. See other connector implementations, notably the CMIS connector (which is similar architecturally) in order to do this right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-344) OpenSearchServer connector needs hiddens to work in multi-tab environment
[ https://issues.apache.org/jira/browse/CONNECTORS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-344: --- Resolution: Fixed Status: Resolved (was: Patch Available) OpenSearchServer connector needs hiddens to work in multi-tab environment - Key: CONNECTORS-344 URL: https://issues.apache.org/jira/browse/CONNECTORS-344 Project: ManifoldCF Issue Type: Bug Components: OpenSearchServer connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: mcf-344-2.patch, mcf-344.patch The OpenSearchServer connector UI loses your data when you click on different tabs in either the output connector configuration page or job page. It needs support for hidden data in order to not do this. See other connector implementations, notably the CMIS connector (which is similar architecturally) in order to do this right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-349) Content binary is not correctly read
[ https://issues.apache.org/jira/browse/CONNECTORS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-349: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF 0.4 r1226302 for release branch Content binary is not correctly read Key: CONNECTORS-349 URL: https://issues.apache.org/jira/browse/CONNECTORS-349 Project: ManifoldCF Issue Type: Bug Components: Alfresco connector Affects Versions: ManifoldCF 0.4 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.4 Original Estimate: 4h Remaining Estimate: 4h In the Alfresco Connector there is a wrong prefix to find the content property for a node. Now I solved this bug, but I have to solve all the conflicts related to the latest changes in the 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
[VOTE] Release apache-manifoldcf-0.4-incubating, RC2
This release candidate has another fix for the Alfresco connector for a problem which prevented it from loading binary data into the search index. Please vote +1 to release RC2. You can find the artifact in the usual place, http://people.apache.org/~kwright/apache-manifoldcf-0.4-incubating. Thanks, Karl
Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC2
I've run all the tests, looks good. +1 for me. Karl On Sun, Jan 1, 2012 at 4:35 PM, Karl Wright daddy...@gmail.com wrote: This release candidate has another fix for the Alfresco connector for a problem which prevented it from loading binary data into the search index. Please vote +1 to release RC2. You can find the artifact in the usual place, http://people.apache.org/~kwright/apache-manifoldcf-0.4-incubating. Thanks, Karl
[jira] [Created] (CONNECTORS-353) It would be an improvement to bundle the SharePoint and Meridio WSDD files into the connector jars as resources
It would be an improvement to bundle the SharePoint and Meridio WSDD files into the connector jars as resources --- Key: CONNECTORS-353 URL: https://issues.apache.org/jira/browse/CONNECTORS-353 Project: ManifoldCF Issue Type: Improvement Components: Build, Meridio connector, SharePoint connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Fix For: ManifoldCF 0.5 The wsdd axis configuration file is currently read as a file from the file system. It would be much more convenient if this could be read as a resource from within the corresponding connector jar. Unfortunately, Axis's FileProvider implementation does not really support this properly. The FileProvider(InputStream) constructor does not properly close the input stream at any point, and in any case allows it to be read only once. The ability to look through the class path is present but starts with the Axis classes (which are not in the connector jar) and also seems to leak file handles. The proper implementation therefore involves someone writing their own ResourceProvider class, implementing EngineConfiguration, with all the right characteristics. This is straightforward but obviously requires testing against a SharePoint instance before it could be committed - or, at least, confirmation the the wsdd configuration is being picked up properly. -- 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] [Assigned] (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 reassigned CONNECTORS-352: -- Assignee: Karl Wright 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-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
Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC1
This looks unrelated to the 0.4-incubating release, which does not have the alfresco multi-tenancy support at all in it. Can you clarify whether you think this is critical for the 0.4-incubating release? That is what the vote thread is for. Karl On Sat, Dec 31, 2011 at 11:32 AM, Piergiorgio Lucidi piergior...@apache.org wrote: I solved the critical issue in the main trunk (r1226128). Hope this helps. Cheers and Happy New Year! Piergiorgio 2011/12/30 Piergiorgio Lucidi piergior...@apache.org: Hi guys, I found a critical bug about the Alfresco Connector, the binary is not correctly managed [1]. I solved the issue, but I have to solve all the conflicts related to the latest changes. I hope to release soon this patch. Cheers, Piergiorgio [1] https://issues.apache.org/jira/browse/CONNECTORS-349 2011/12/29 Karl Wright daddy...@gmail.com: I've uploaded the RC1 apache-manifoldcf-0.4-incubating package which you can download from http://people.apache.org/~kwright. If you agree this should be released please vote +1. The fixes over RC0 are all UI related; you can see what they are in the CHANGES.txt file. Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com
[jira] [Created] (CONNECTORS-347) MySQL HopCount test sometimes fails
MySQL HopCount test sometimes fails
---
Key: CONNECTORS-347
URL: https://issues.apache.org/jira/browse/CONNECTORS-347
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.5
The HopcountMySQLIT test sometimes fails complaining that it is expecting to
see 6 documents but only sees 4.
{code}
[junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong
number of documents processed - expected 6, saw 4
[junit] at
org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152)
{code}
This does not happen on every run.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-341) override config for test cases
[ https://issues.apache.org/jira/browse/CONNECTORS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177643#comment-13177643 ] Karl Wright commented on CONNECTORS-341: bq. Do all test have to sub class a DBMS specific Base class like DerbyBase? It is hard to imagine a test that does not need database functionality, but if you have a unit test that is standalone and does not, then no you do not need to subclass anything. See connectors/rss/connector/src/test/java/org/apache/manifoldcf/crawler/connectors/rss/tests for examples. override config for test cases -- Key: CONNECTORS-341 URL: https://issues.apache.org/jira/browse/CONNECTORS-341 Project: ManifoldCF Issue Type: Improvement Components: Tests Reporter: Martin Goldhahn Attachments: CONNECTORS-341.patch It is hard to write a test case for a repository connector using the existing *.Base classes that uses a different config file. The config files are actually written in org.apache.manifoldcf.core.tests.Base.localSetup(). The localSetup method is called by all sub-classes in their overridden localSetup function. each sub-class adds something specific for the test case. If I wanted to put something different in the config files I had to override localSetup() and copy all content of the superclasses' localSetup to it. This can be avoided by moving the code that writes the config file in the initialize() method. It makes also more sense in that the creation of the config files and the provision of their content are now in the same function. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-343) Severe connector UI bugs
[
https://issues.apache.org/jira/browse/CONNECTORS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177227#comment-13177227
]
Karl Wright commented on CONNECTORS-343:
r1225559 for the rest of it.
Severe connector UI bugs
Key: CONNECTORS-343
URL: https://issues.apache.org/jira/browse/CONNECTORS-343
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector, CMIS connector, OpenSearchServer
connector
Affects Versions: ManifoldCF 0.4
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Critical
Fix For: ManifoldCF 0.4
There are various severe UI bugs with the Alfresco connector, CMIS connector,
and OpenSearchServer connector. These include:
- injection of ${XXX} data into fields on the first (re)post of each edit
form (Alfresco and CMIS only)
- no escaping of string values appropriate for the context of each
substitution value, which means the forms will blow up when unusual values
like or are included in (say) a password
I've fixed these problems on trunk as part of CONNECTORS-335. This ticket is
meant to capture the problem for the 0.4 release.
--
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
[VOTE] Release apache-manifoldcf-0.4-incubating, RC1
I've uploaded the RC1 apache-manifoldcf-0.4-incubating package which you can download from http://people.apache.org/~kwright. If you agree this should be released please vote +1. The fixes over RC0 are all UI related; you can see what they are in the CHANGES.txt file. Karl
Re: [VOTE] Release Apache ManifoldCF 0.4-incubating, RC0
I found a potential blocker for 0.4-incubator, CONNECTORS-342. I
think it is severe enough to require respin of the candidate. The bad
HTML causes the Save button to vanish and makes the File Connector
only barely usable.
I've also found UI problems with the CMIS and Alfresco connectors; the
way hiddens are managed is incorrect so that you can get ${xxx} values
stuffed in the fields on the initial post/repost. In addition they
both suffer from lack of proper escaping of values in the UI. The
OpenSearchServer connector also suffers from the latter. These bugs
are pretty severe in my opinion and I've captured them in
CONNECTORS-343.
I've checked in a fix to the branch for CONNECTORS-342. The fix for
CONNECTORS-343 is a bit more extensive but is certainly doable within
the 0.4-incubating release. Piergiorgio, do you agree that we should
try to fix this for this release?
Karl
On Tue, Dec 20, 2011 at 8:40 AM, Karl Wright daddy...@gmail.com wrote:
As long as your changes are committed to trunk, I can push them to the
site immediately. They just won't be in the documentation that ships
with ManifoldCF 0.4-incubating, is all.
So it sounds like we have a vote to release, as soon as we wait the
full 72 hours. ;-)
Karl
On Tue, Dec 20, 2011 at 8:33 AM, Piergiorgio Lucidi
piergior...@apache.org wrote:
2011/12/20 Karl Wright daddy...@gmail.com:
Piergiorgio wants to include a section in the how to build and
deploy documentation for the Alfresco connector. To me this is not
really an important enough change to spin another RC, but since we're
still waiting for Tommaso to review our releases there may be time to
do it.
But, right now, I vote +1 for RC0. We'll see if Piergiorgio withdraws his
vote.
It's not a problem for me to release this RC0, but I would like to
update at least the website documentation about how to build the
Alfresco Connector. I hope this night to work on this new section and
then we can push an update of the website.
Piergiorgio
Karl
On Mon, Dec 19, 2011 at 7:04 PM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
Thank you. I understand.
+1 for me.
Shinichiro Abe
On 2011/12/19, at 16:25, Karl Wright wrote:
The hsqldb configuration used by multiprocess-example is an external
hsqldb database. It does not require the
org.apache.manifoldcf.hsqldbdatabasepath property. If you want to try
out the multiprocess example, take the following steps:
(1) In one shell prompt, start the database: start-database.bat/.sh
(2) In another shell prompt, initialize the database: initialize.bat/.sh
(3) When that is done, start the agents proces: start-agents.bat/.sh
Thanks,
Karl
On Mon, Dec 19, 2011 at 2:05 AM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
Hi.
I checked 0.4 by running ant test, okay but one problem.
In multiprocess-example, at default properties.xml, HSQLDB database
requires
'org.apache.manifoldcf.hsqldbdatabasepath' property, containing a
relative path:
property name=org.apache.manifoldcf.hsqldbdatabasepath value=./
Now exception is thrown, so we need to add this property.
Should I send a patch? Next?
Regards,
Shinichiro Abe
On 2011/12/18, at 2:27, Karl Wright wrote:
I've again uploaded an apache-manifoldcf-0.4-incubating package which
you
can download from http://people.apache.org/~kwright. If you agree
this should be released please vote +1.
[Note that the release of this artifact is dependent on the release of
the three plugin packages upon which it depends. If we need to change
those packages we'll need to spin a new RC of this one. Also please
note that I've include SHA1 signatures for the first time, as per
Jukka's suggestion.]
I apologize again for the earlier hiccup. This one is the real thing,
though, and passes all tests.
Thanks!
Karl
--
Piergiorgio Lucidi
http://www.open4dev.com
[jira] [Commented] (CONNECTORS-344) OpenSearchServer connector needs hiddens to work in multi-tab environment
[ https://issues.apache.org/jira/browse/CONNECTORS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177236#comment-13177236 ] Karl Wright commented on CONNECTORS-344: Nobody has started. If you want to submit a patch, that would be great! Thanks! OpenSearchServer connector needs hiddens to work in multi-tab environment - Key: CONNECTORS-344 URL: https://issues.apache.org/jira/browse/CONNECTORS-344 Project: ManifoldCF Issue Type: Bug Components: OpenSearchServer connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The OpenSearchServer connector UI loses your data when you click on different tabs in either the output connector configuration page or job page. It needs support for hidden data in order to not do this. See other connector implementations, notably the CMIS connector (which is similar architecturally) in order to do this right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-344) OpenSearchServer connector needs hiddens to work in multi-tab environment
OpenSearchServer connector needs hiddens to work in multi-tab environment - Key: CONNECTORS-344 URL: https://issues.apache.org/jira/browse/CONNECTORS-344 Project: ManifoldCF Issue Type: Bug Components: OpenSearchServer connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The OpenSearchServer connector UI loses your data when you click on different tabs in either the output connector configuration page or job page. It needs support for hidden data in order to not do this. See other connector implementations, notably the CMIS connector (which is similar architecturally) in order to do this right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-341) override config for test cases
[ https://issues.apache.org/jira/browse/CONNECTORS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177157#comment-13177157 ] Karl Wright commented on CONNECTORS-341: bq. I suggest... Two comments. First, maybe I didn't understand your use case - I was thinking that you meant that one might want to write a derived test which set different parameters than the ones included in the base class. But now you are talking about setting parameters based on files described by a -D switch? I'm not convinced this is appropriate. Second, you can't create two configuration files with one String return value. :-) Your createConfigFiles() method seems to attempt to do just that. Another question I have is whether it is ever appropriate to NOT clean up configuration files when the test is done. Other subsequent tests will lay down their own configuration files, and in the same folder/directory. Not cleaning up invites confusion, seems to me. override config for test cases -- Key: CONNECTORS-341 URL: https://issues.apache.org/jira/browse/CONNECTORS-341 Project: ManifoldCF Issue Type: Improvement Components: Tests Reporter: Martin Goldhahn Attachments: CONNECTORS-341.patch It is hard to write a test case for a repository connector using the existing *.Base classes that uses a different config file. The config files are actually written in org.apache.manifoldcf.core.tests.Base.localSetup(). The localSetup method is called by all sub-classes in their overridden localSetup function. each sub-class adds something specific for the test case. If I wanted to put something different in the config files I had to override localSetup() and copy all content of the superclasses' localSetup to it. This can be avoided by moving the code that writes the config file in the initialize() method. It makes also more sense in that the creation of the config files and the provision of their content are now in the same function. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-346) Testing hierarchy needs work
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 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] [Commented] (CONNECTORS-342) File connector Paths tab has broken html
[ https://issues.apache.org/jira/browse/CONNECTORS-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177119#comment-13177119 ] Karl Wright commented on CONNECTORS-342: A fix for this issue has already been checked into trunk as part of CONNECTORS-339. This ticket thus only covers the 0.4-incubating release. 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] [Issue Comment Edited] (CONNECTORS-341) override config for test cases
[
https://issues.apache.org/jira/browse/CONNECTORS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177124#comment-13177124
]
Karl Wright edited comment on CONNECTORS-341 at 12/29/11 11:53 AM:
---
I had been toying with moving these embedded configuration files to
src/test/resource instead. It sounds like that would mess up your use case
entirely though.
I like the fact that initialize() can be separately overridden, but I'd like
perhaps to take it a step further and provide a base class method that is
specifically meant to be overridden such that the values written can be
extended rather than completely replaced, e.g.:
{code}
protected void populateConfigurationXML(StringBuilder sb)
{
...
}
{code}
... which is called from the base class implementation of initialize(). Also a
similar method for logging.ini. Do you understand what I mean, and if so do
you want to modify your patch accordingly?
was (Author: kwri...@metacarta.com):
I had been toying with moving these embedded configuration files to
src/test/resource instead. It sounds like that would mess up your use case
entirely though.
I like the fact that initialize() can be separately overridden, but I'd like
perhaps to take it a step further and provide a base class method that is
specifically meant to be overridden such that the values written can be
extended rather than completely replaced, e.g.:
protected void populateConfigurationXML(StringBuilder sb)
{
...
}
... which is called from the base class implementation of initialize(). Also a
similar method for logging.ini. Do you understand what I mean, and if so do
you want to modify your patch accordingly?
override config for test cases
--
Key: CONNECTORS-341
URL: https://issues.apache.org/jira/browse/CONNECTORS-341
Project: ManifoldCF
Issue Type: Improvement
Components: Tests
Reporter: Martin Goldhahn
Attachments: CONNECTORS-341.patch
It is hard to write a test case for a repository connector using the existing
*.Base classes that uses a different config file.
The config files are actually written in
org.apache.manifoldcf.core.tests.Base.localSetup().
The localSetup method is called by all sub-classes in their overridden
localSetup function. each sub-class adds something specific for the test
case. If I wanted to put something different in the config files I had to
override localSetup() and copy all content of the superclasses' localSetup to
it. This can be avoided by moving the code that writes the config file in the
initialize() method. It makes also more sense in that the creation of the
config files and the provision of their content are now in the same function.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-346) Testing hierarchy needs work
[ https://issues.apache.org/jira/browse/CONNECTORS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-346: --- Fix Version/s: ManifoldCF 0.5 Assignee: Karl Wright 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] [Commented] (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:comment-tabpanelfocusedCommentId=13177356#comment-13177356 ] Karl Wright commented on CONNECTORS-337: r1225633 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 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-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] [Commented] (CONNECTORS-346) Testing hierarchy needs work
[ https://issues.apache.org/jira/browse/CONNECTORS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177393#comment-13177393 ] Karl Wright commented on CONNECTORS-346: r1225655 for pulling loadtests out of their own hierarchy into the integration test hierarchy. 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] [Commented] (CONNECTORS-345) Jetty Configuration Support
[ https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177465#comment-13177465 ] Karl Wright commented on CONNECTORS-345: bq. It looks like some things have changed going from Jetty 6.1.26 and the newest version 7.x. So, the dependencies for this will change a bit. This is kind of what I was afraid of. If it's relatively easy to port to using Jetty 7 I'd certainly be willing to do it in the release 0.5 timeframe. If there are broad architectural changes, and/or your requirements are going to require ManifoldCF to continuously upgrade Jetty versions, then it's more of a tradeoff. It should be pretty easy to see if Jetty 7 works right now with MCF, and that would be the proper first step. Just delete the old jetty*.jar files from the lib directory, drop down the new jetty jar files, and try running ant test. If that fails we'd need to figure out why. (The single-process example will almost certainly fail because start.jar won't have the right manifest, but that is easy to address.) Jetty Configuration Support --- Key: CONNECTORS-345 URL: https://issues.apache.org/jira/browse/CONNECTORS-345 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.4 Environment: Jetty Configuration Reporter: Michael J. Kelleher Can the single process example be extended to support Jetty configuration? 1) jetty.xml 2) webdefault.xml 3) OPTIONS= along with their corresponding XML config files, most importantly the JMX option, Server,ajp,setuid would be nice to have -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-346) Testing hierarchy needs work
[ https://issues.apache.org/jira/browse/CONNECTORS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177527#comment-13177527 ] Karl Wright commented on CONNECTORS-346: r1225740 to create a common infrastructure for firing up a ManifoldCF instance. 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] [Updated] (CONNECTORS-338) Localization data in the wrong place
[ https://issues.apache.org/jira/browse/CONNECTORS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-338: --- Affects Version/s: ManifoldCF 0.5 Fix Version/s: ManifoldCF 0.5 Localization data in the wrong place Key: CONNECTORS-338 URL: https://issues.apache.org/jira/browse/CONNECTORS-338 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 The localization data for the Crawler UI is currently put in the core jar. It should really be moved to the ui-core jar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-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:comment-tabpanelfocusedCommentId=13176637#comment-13176637 ] Karl Wright commented on CONNECTORS-339: r1225139 to get the basic framework going. This requires Python to be installed at the moment, but we can later port it entirely to native Java. 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] [Commented] (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:comment-tabpanelfocusedCommentId=13176752#comment-13176752 ] Karl Wright commented on CONNECTORS-339: r1225267 to add locale support. 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] [Commented] (CONNECTORS-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177047#comment-13177047 ] Karl Wright commented on CONNECTORS-314: bq. Just want to make sure again. Should I be getting the source code from the trunk now? Where are fixes for the CONNECTORS-338 and CONNECTORS-340 being committed? All fixes have now been committed to trunk EXCEPT for the Japanese documentation, which is still going into branches/CONNECTORS-336. Combined MySQL and i18n/Japanese contribution - Key: CONNECTORS-314 URL: https://issues.apache.org/jira/browse/CONNECTORS-314 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Labels: I18N, mysql Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-314-20111225.patch, CONNECTORS-314-doc20111220.patch, CONNECTORS-314.patch, CONNECTORS-314.patch, connectors.patch, framework.patch Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and MySQL database support, all in one 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] [Issue Comment Edited] (CONNECTORS-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13177047#comment-13177047 ] Karl Wright edited comment on CONNECTORS-314 at 12/29/11 7:50 AM: -- bq. Just want to make sure again. Should I be getting the source code from the trunk now? Where are fixes for the CONNECTORS-338 and CONNECTORS-340 being committed? All fixes have now been committed to trunk EXCEPT for the Japanese documentation, which is still going into branches/CONNECTORS-336. I'm also working on automated tests for the UI. Currently I'm testing just en_US, but I hope to add a set of ja_JP tests as well. As I go I am running into and fixing various minor UI bugs. That ticket is CONNECTORS-339, which is still open. was (Author: kwri...@metacarta.com): bq. Just want to make sure again. Should I be getting the source code from the trunk now? Where are fixes for the CONNECTORS-338 and CONNECTORS-340 being committed? All fixes have now been committed to trunk EXCEPT for the Japanese documentation, which is still going into branches/CONNECTORS-336. Combined MySQL and i18n/Japanese contribution - Key: CONNECTORS-314 URL: https://issues.apache.org/jira/browse/CONNECTORS-314 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Labels: I18N, mysql Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-314-20111225.patch, CONNECTORS-314-doc20111220.patch, CONNECTORS-314.patch, CONNECTORS-314.patch, connectors.patch, framework.patch Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and MySQL database support, all in one 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] [Commented] (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:comment-tabpanelfocusedCommentId=13177050#comment-13177050 ] Karl Wright commented on CONNECTORS-339: r1225461 saves a job, and then deletes it. 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] [Commented] (CONNECTORS-335) Internationalize ManifoldCF and add a Japanese translation
[ https://issues.apache.org/jira/browse/CONNECTORS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176193#comment-13176193 ] Karl Wright commented on CONNECTORS-335: r1224921 to insure that all Messages.getString() use the browser's preferred locale. Internationalize ManifoldCF and add a Japanese translation -- Key: CONNECTORS-335 URL: https://issues.apache.org/jira/browse/CONNECTORS-335 Project: ManifoldCF Issue Type: Improvement Components: Build, Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 We need to internationalize the ManifoldCF screens so that multiple language support is possible. While we're at it, let's provide localizations for English and Japanese. (This ticket is meant to include contributions contained in CONNECTORS-314.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176208#comment-13176208 ] Karl Wright commented on CONNECTORS-314: bq. I want to get it to a situation where I can introduce this to Japanese users quickly as possible. I think most are going to use just Solr, AD, File, DB, and Web with MySQL. That's fine, although MySQL is not yet been certified to scale with ManifoldCF, unlike PostgreSQL. bq. There's also some issues that I've been notified - mainly concerning performance when there are over 1 million files to crawl. I'll createissues concerning these after finishing up the above topics. This is exactly what I mean. Any fully-supported database implementation must be capable of performing certain queries reliably and quickly. The MySQL implementation currently is functional, but has not been assessed or tuned for this kind of performance. Typically this requires quite a lot of time - the HSQLDB implementation just achieved this goal despite being available for most of the last year. It may even not be possible to achieve. The HSQLDB implementation required HSQLDB improvements to make it possible. Hopefully that will not be needed for MySQL but there are no guarantees. But we won't even know that until much more time has been invested. Combined MySQL and i18n/Japanese contribution - Key: CONNECTORS-314 URL: https://issues.apache.org/jira/browse/CONNECTORS-314 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Labels: I18N, mysql Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-314-20111225.patch, CONNECTORS-314-doc20111220.patch, CONNECTORS-314.patch, CONNECTORS-314.patch, connectors.patch, framework.patch Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and MySQL database support, all in one 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] [Updated] (CONNECTORS-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-314: --- Resolution: Fixed Status: Resolved (was: Patch Available) The work in this ticket has been completely replaced by tickets CONNECTORS-334, CONNECTORS-335, and CONNECTORS-336. Combined MySQL and i18n/Japanese contribution - Key: CONNECTORS-314 URL: https://issues.apache.org/jira/browse/CONNECTORS-314 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Labels: I18N, mysql Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-314-20111225.patch, CONNECTORS-314-doc20111220.patch, CONNECTORS-314.patch, CONNECTORS-314.patch, connectors.patch, framework.patch Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and MySQL database support, all in one 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] [Created] (CONNECTORS-337) Maven build -DskipIT does not seem to skip integration tests anymore
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 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] [Commented] (CONNECTORS-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176021#comment-13176021 ] Karl Wright commented on CONNECTORS-314: The MySQL work was already committed directly to trunk. The i18n work is in branches/CONNECTORS-335 and is ready to commit except for one problem: it breaks the Maven build. So as soon as that is fixed the commit will happen. branches/CONNECTORS-336 contains the documentation changes which will also be committed to trunk when that is ready, which I presume will take a while. Hope this helps! Combined MySQL and i18n/Japanese contribution - Key: CONNECTORS-314 URL: https://issues.apache.org/jira/browse/CONNECTORS-314 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Labels: I18N, mysql Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-314-20111225.patch, CONNECTORS-314-doc20111220.patch, CONNECTORS-314.patch, CONNECTORS-314.patch, connectors.patch, framework.patch Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and MySQL database support, all in one 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
