[jira] [Created] (CONNECTORS-252) clean up build, dist and lib of each connector after build
clean up build, dist and lib of each connector after build -- Key: CONNECTORS-252 URL: https://issues.apache.org/jira/browse/CONNECTORS-252 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-252.patch After running ant build, folder size increases about five times. Building resources in connectors are expected not to use, except for test output. I want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101047#comment-13101047 ] Karl Wright commented on CONNECTORS-250: Shinichiro, you should go ahead and commit this. Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101048#comment-13101048 ] Karl Wright commented on CONNECTORS-251: We cannot redistribute jcifs.jar, but the code can certainly download it. So you can go ahead and commit this patch too. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101050#comment-13101050 ] Karl Wright commented on CONNECTORS-251: Final comment: Since we build the images for distribution using ant, we need some way of PREVENTING the download in that case. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101049#comment-13101049 ] Karl Wright commented on CONNECTORS-251: The only caution I have is that, if the person is running off of the net, the download might fail. The conditional logic looks like it would catch that situation though. Just so long as the build does not fail in that case. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 0.3-incubating RC0 available for inspection
I get: C:\wip\mcf\trunk\frameworkant run-script-engine-tests Buildfile: C:\wip\mcf\trunk\framework\build.xml compile-core: [javac] C:\wip\mcf\trunk\framework\build.xml:47: warning: 'includeantruntime ' was not set, defaulting to build.sysclasspath=last; set to false for repeatabl e builds compile-script-engine: [javac] C:\wip\mcf\trunk\framework\build.xml:109: warning: 'includeantruntim e' was not set, defaulting to build.sysclasspath=last; set to false for repeatab le builds compile-script-engine-tests: [javac] C:\wip\mcf\trunk\framework\build.xml:515: warning: 'includeantruntim e' was not set, defaulting to build.sysclasspath=last; set to false for repeatab le builds run-script-engine-tests: [mkdir] Created dir: C:\wip\mcf\trunk\framework\test-output [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.586 sec [junit] [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.CommandTest [junit] hello [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.07 sec [junit] [junit] - Standard Output --- [junit] hello [junit] - --- BUILD SUCCESSFUL This target can only be run directly after the top-level ant build is run. If you run the test at the top level (ant tests) the script test is also called. What does your output look like? Karl On Fri, Sep 9, 2011 at 3:28 AM, Karl Wright daddy...@gmail.com wrote: Test failure is not ok. Let me try it here. Karl On Fri, Sep 9, 2011 at 12:48 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Hello. I tested sharedrive connector/ authority connector on 0.3RC0 and confirmed changes. It worked well. BTW, ant run-script-engine-tests said build failed. The same error is in trunk . Is it okay? Regards, Shinichiron Abe On 2011/09/08, at 8:17, Karl Wright wrote: You can find it here: http://people.apache.org/~kwright/apache-manifoldcf-0.3-incubating/ There have been a number of significant changes this release, so I think it's a good idea if at least one other person has a thorough look at it. Karl
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101058#comment-13101058 ] Karl Wright commented on CONNECTORS-251: Thinking further on this, making this completely automatic won't work because there's no good way in ant to make one dependency of a target fire before another dependency of the same target, without linking the two dependencies together. So instead I'd propose we introduce a new root-level target as well, download-dependencies, which does the job of picking up the non-redistributable dependencies for all connectors. In practice this will just be the jcifs.jar at this time. But the build structure should support each connector making the determination of what to download. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 0.3-incubating RC0 available for inspection
Is my environment wrong, or something like CRLF, locale? I checked out a few minuites ago and run test. I get: abe:~ abe$ cd /Users/abe/Desktop/new/trunk/framework/ abe:framework abe$ ant run-script-engine-tests Buildfile: /Users/abe/Desktop/new/trunk/framework/build.xml compile-core: [javac] /Users/abe/Desktop/new/trunk/framework/build.xml:47: warning: 'includeantruntime ' was not set, defaulting to build.sysclasspath=last; set to false for repeatabl e builds compile-script-engine: [javac] /Users/abe/Desktop/new/trunk/framework/build.xml:109: warning: 'includeantruntime ' was not set, defaulting to build.sysclasspath=last; set to false for repeatabl e builds compile-script-engine-tests: [javac] /Users/abe/Desktop/new/trunk/framework/build.xml:515: warning: 'includeantruntime ' was not set, defaulting to build.sysclasspath=last; set to false for repeatabl e builds run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED /Users/abe/Desktop/new/trunk/framework/build.xml:554: Test org.apache.manifoldcf.scriptengine.tests.ExpressionTest failed Regards, Shinichiro Abe On 2011/09/09, at 16:33, Karl Wright wrote: I get: C:\wip\mcf\trunk\frameworkant run-script-engine-tests Buildfile: C:\wip\mcf\trunk\framework\build.xml compile-core: [javac] C:\wip\mcf\trunk\framework\build.xml:47: warning: 'includeantruntime ' was not set, defaulting to build.sysclasspath=last; set to false for repeatabl e builds compile-script-engine: [javac] C:\wip\mcf\trunk\framework\build.xml:109: warning: 'includeantruntim e' was not set, defaulting to build.sysclasspath=last; set to false for repeatab le builds compile-script-engine-tests: [javac] C:\wip\mcf\trunk\framework\build.xml:515: warning: 'includeantruntim e' was not set, defaulting to build.sysclasspath=last; set to false for repeatab le builds run-script-engine-tests: [mkdir] Created dir: C:\wip\mcf\trunk\framework\test-output [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.586 sec [junit] [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.CommandTest [junit] hello [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.07 sec [junit] [junit] - Standard Output --- [junit] hello [junit] - --- BUILD SUCCESSFUL This target can only be run directly after the top-level ant build is run. If you run the test at the top level (ant tests) the script test is also called. What does your output look like? Karl On Fri, Sep 9, 2011 at 3:28 AM, Karl Wright daddy...@gmail.com wrote: Test failure is not ok. Let me try it here. Karl On Fri, Sep 9, 2011 at 12:48 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Hello. I tested sharedrive connector/ authority connector on 0.3RC0 and confirmed changes. It worked well. BTW, ant run-script-engine-tests said build failed. The same error is in trunk . Is it okay? Regards, Shinichiron Abe On 2011/09/08, at 8:17, Karl Wright wrote: You can find it here: http://people.apache.org/~kwright/apache-manifoldcf-0.3-incubating/ There have been a number of significant changes this release, so I think it's a good idea if at least one other person has a thorough look at it. Karl
Re: 0.3-incubating RC0 available for inspection
At first, I saw the error during ant test after running ant clean build. Then, I run run-script-engine-tests at framework. Now, in my computer, ant test does not work successfully.
[jira] [Created] (CONNECTORS-253) Script test fails on some machines due to hash order
Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-253) Script test fails on some machines due to hash order
[ https://issues.apache.org/jira/browse/CONNECTORS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-253: -- Assignee: Karl Wright Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-253) Script test fails on some machines due to hash order
[ https://issues.apache.org/jira/browse/CONNECTORS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101066#comment-13101066 ] Karl Wright commented on CONNECTORS-253: r1167039 in trunk. r1167043 in release-0.3-incubating branch. Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-253) Script test fails on some machines due to hash order
[ https://issues.apache.org/jira/browse/CONNECTORS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-253. Resolution: Fixed Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-250. --- Resolution: Fixed r1167057 Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-252. --- Resolution: Fixed r1167058 clean up build, dist and lib of each connector after build -- Key: CONNECTORS-252 URL: https://issues.apache.org/jira/browse/CONNECTORS-252 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-252.patch After running ant build, folder size increases about five times. Building resources in connectors are expected not to use, except for test output. I want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-251: -- Attachment: CONNECTORS-251-1.patch When selecting download-dependencies, is it better for user to select download target again(display echo)? jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-251-1.patch, CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 0.3-incubating RC0 available for inspection
Thanks for the test! I'll put up a new RC shortly. Karl On Fri, Sep 9, 2011 at 5:24 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: I finished to run test successfully on trunk code. No problem. Thank you. Shinichiro Abe On 2011/09/09, at 17:39, Karl Wright wrote: It should be fixed on trunk now. I'll have to spin an RC1 later today for the release. Please confirm that it works for you now on trunk. Karl On Fri, Sep 9, 2011 at 4:25 AM, Karl Wright daddy...@gmail.com wrote: I know what the problem is - it's a different hash order on your machine than on mine, probably due to a different JVM. I'll have to fix this (or disable that one test). Karl On Fri, Sep 9, 2011 at 4:20 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: At first, I saw the error during ant test after running ant clean build. Then, I run run-script-engine-tests at framework. Now, in my computer, ant test does not work successfully.
[jira] [Updated] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-250: --- Fix Version/s: (was: ManifoldCF 0.4) ManifoldCF 0.3 Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101116#comment-13101116 ] Karl Wright commented on CONNECTORS-250: r1167088 for release-0.3-incubating branch. Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Keller updated CONNECTORS-240: --- Attachment: opensearchserver-connection-parameters.PNG OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: opensearchserver-connection-parameters.PNG, oss-mfc-doc.patch, oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Keller updated CONNECTORS-240: --- Attachment: (was: opensearchserver-connection-parameters.PNG) OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: opensearchserver-connection-parameters.PNG, opensearchserver-history-report.PNG, opensearchserver-job-parameters.PNG, oss-mfc-doc.patch, oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Keller updated CONNECTORS-240: --- Attachment: opensearchserver-history-report.PNG OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: opensearchserver-connection-parameters.PNG, opensearchserver-history-report.PNG, opensearchserver-job-parameters.PNG, oss-mfc-doc.patch, oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Keller updated CONNECTORS-240: --- Attachment: opensearchserver-user.PNG OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: opensearchserver-connection-parameters.PNG, opensearchserver-history-report.PNG, opensearchserver-job-parameters.PNG, opensearchserver-user.PNG, oss-mfc-doc.patch, oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-240. Resolution: Fixed r1167110 (trunk) OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: opensearchserver-connection-parameters.PNG, opensearchserver-history-report.PNG, opensearchserver-job-parameters.PNG, opensearchserver-user.PNG, oss-mfc-doc.patch, oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 0.3-incubating RC0 available for inspection
Hi Tobias, The maven instructions have already been properly updated, but I haven't pushed it to the mirror yet. Once I do that you should see the changes. Karl On Fri, Sep 9, 2011 at 10:54 AM, Tobias Rübner d...@tobr.eu wrote: Hi Karl, I checked out the RC1 und did a mvn clean install on the root to test the build using the maven integration. HSQLDB is now included in a new version (2.2.5.6-9-2011) which is not available in the maven repositories. So maybe you can add it to the list of additional dependencies for building with maven. http://incubator.apache.org/connectors/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Maven Tobias On Fri, Sep 9, 2011 at 2:29 PM, Karl Wright daddy...@gmail.com wrote: There's now an RC1 uploaded at http://people.apache.org/~kwright. Please check it out - I'll be calling a formal vote on it soon! Karl On Fri, Sep 9, 2011 at 6:50 AM, Karl Wright daddy...@gmail.com wrote: Thanks for the test! I'll put up a new RC shortly. Karl On Fri, Sep 9, 2011 at 5:24 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: I finished to run test successfully on trunk code. No problem. Thank you. Shinichiro Abe On 2011/09/09, at 17:39, Karl Wright wrote: It should be fixed on trunk now. I'll have to spin an RC1 later today for the release. Please confirm that it works for you now on trunk. Karl On Fri, Sep 9, 2011 at 4:25 AM, Karl Wright daddy...@gmail.com wrote: I know what the problem is - it's a different hash order on your machine than on mine, probably due to a different JVM. I'll have to fix this (or disable that one test). Karl On Fri, Sep 9, 2011 at 4:20 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: At first, I saw the error during ant test after running ant clean build. Then, I run run-script-engine-tests at framework. Now, in my computer, ant test does not work successfully.
[VOTE] Release ManifoldCF 0.3-incubating, RC1
You can download the release candidate from http://people.apache.org/~kwright, and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags. +1 to release this RC. -1 to not release it. After a successful release vote, please be aware that I will need to present the release candidate to the incubator for their vote as well, before the release is actually made. Karl
Re: [VOTE] Release ManifoldCF 0.3-incubating, RC1
+1 from me. Karl On Fri, Sep 9, 2011 at 1:41 PM, Karl Wright daddy...@gmail.com wrote: You can download the release candidate from http://people.apache.org/~kwright, and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags. +1 to release this RC. -1 to not release it. After a successful release vote, please be aware that I will need to present the release candidate to the incubator for their vote as well, before the release is actually made. Karl
[jira] [Updated] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-202: --- Affects Version/s: ManifoldCF 0.3 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.4 Assignee: Karl Wright SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-87) Connector Framework load test needs to be written
[ https://issues.apache.org/jira/browse/CONNECTORS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-87: -- Affects Version/s: ManifoldCF 0.3 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.4 Assignee: Karl Wright Connector Framework load test needs to be written - Key: CONNECTORS-87 URL: https://issues.apache.org/jira/browse/CONNECTORS-87 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 LCF needs a load or performance test, which verifies that the core software is performing as expected. This test can use the file system connector, but must verify that individual throttle bins are getting approximately equal time, and that the system as a whole is behaving efficiently. Furthermore, at least 1,000,000 documents should be crawled by this test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101584#comment-13101584 ] Jan Høydahl commented on CONNECTORS-202: Solr 3.4 is being released as we speak, will hit the road in a few days. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101586#comment-13101586 ] Karl Wright commented on CONNECTORS-202: MCF 0.3 RC1 is currently under review as well. I've triaged this ticket for the 0.4 release. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101596#comment-13101596 ] Jan Høydahl commented on CONNECTORS-202: That's ok, people can set commitWithin in Solr OutputConnector as a workaround. I'm not familiar with MCF code, but will see if I get back to a patch attempt later. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
