Re: Build failed in Hudson: Lucene-trunk #1313
[junit] # [junit] # An unexpected error has been detected by HotSpot Virtual Machine: [junit] # [junit] # SIGSEGV (0xb) at pc=0x0008010c22f2, pid=21897, tid=0xc08ec0 [junit] # [junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_16-p9-root_01_oct_2010_23_12 mixed mode) [junit] # Problematic frame: [junit] # V [libjvm.so+0x2c22f2] [junit] # [junit] # An error report file with more information is saved as hs_err_pid21897.log [junit] # [junit] # If you would like to submit a bug report, please write [junit] # a letter to freebsd-j...@freebsd.org mailing list [junit] # ouch! uwe can we get the error log somehow to figure out if that is a known issue - wouldn't be the first time we run into a jvm bug. This seems to be a hand build JVM and the FreeBSD project doesn't seem to continue maintaining 1.5 JVMs though... hmm maybe we need to go to 1.6 on freebsd though or use 1.5 for compiling. not sure but to use hudson to run multiple jvms we might need to use Linux rather then BSD though. On Sun, Oct 3, 2010 at 4:34 AM, Apache Hudson Server hud...@hudson.apache.org wrote: See https://hudson.apache.org/hudson/job/Lucene-trunk/1313/changes Changes: [rmuir] clear up more compiler warnings [rmuir] clear up more compiler warnings [rmuir] add missing eol-style [rmuir] add missing eol-style [rmuir] clean up some fallthru/deprecation warnings [rmuir] clean up some fallthru/deprecation warnings [rmuir] remove useless casts [rmuir] clear up some easy warnings [rmuir] enable more violations from compile [simonw] LUCENE-2662: Refactored TermsHashPerField to utilize ByteRefHash [uschindler] remove useless maven lib support (is included on hudson's ant) [simonw] LUCENE-2677: Tests failing when run with tests.iter 1 -- [...truncated 14344 lines...] [javadoc] Building index for all the packages and classes... [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/misc/src/java/org/apache/lucene/store/DirectIOLinuxDirectory.java:44: warning - Tag @link: reference not found: Directory [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-misc/stylesheet.css... [javadoc] Note: Custom tags that were not seen: �...@lucene.internal [javadoc] 5 warnings [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/contrib/misc/lucene-misc-4.0-2010-10-03_02-03-18-javadoc.jar [echo] Building queries... javadocs: [mkdir] Created dir: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-queries [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package org.apache.lucene.search... [javadoc] Loading source files for package org.apache.lucene.search.regex... [javadoc] Loading source files for package org.apache.lucene.search.similar... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.5.0_16-p9 [javadoc] Building tree for all the packages and classes... [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/JakartaRegexpCapabilities.java:35: warning - Tag @link: can't find prefix in org.apache.lucene.search.regex.JakartaRegexpCapabilities [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.java:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.java:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/JavaUtilRegexCapabilities.java:33: warning - Tag @link: can't find prefix in org.apache.lucene.search.regex.JavaUtilRegexCapabilities [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/JavaUtilRegexCapabilities.java:33: warning - Tag @link: can't find match in org.apache.lucene.search.regex.JavaUtilRegexCapabilities [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.java:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contrib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.java:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc]
RE: Build failed in Hudson: Lucene-trunk #1313
We have an issue open at infra to enable linprocfs mount in the jail, so we can use the official Linux 32 bit JVMs to build Lucene/Solr (in addition to base_linux package). This may take some time, until then we only have old versions of both 1.6.0_openjdk(unknown bugfixlevel) and 1.5.0_16. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Simon Willnauer [mailto:simon.willna...@googlemail.com] Sent: Sunday, October 03, 2010 9:33 AM To: dev@lucene.apache.org Subject: Re: Build failed in Hudson: Lucene-trunk #1313 [junit] # [junit] # An unexpected error has been detected by HotSpot Virtual Machine: [junit] # [junit] # SIGSEGV (0xb) at pc=0x0008010c22f2, pid=21897, tid=0xc08ec0 [junit] # [junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_16-p9-root_01_oct_2010_23_12 mixed mode) [junit] # Problematic frame: [junit] # V [libjvm.so+0x2c22f2] [junit] # [junit] # An error report file with more information is saved as hs_err_pid21897.log [junit] # [junit] # If you would like to submit a bug report, please write [junit] # a letter to freebsd-j...@freebsd.org mailing list [junit] # ouch! uwe can we get the error log somehow to figure out if that is a known issue - wouldn't be the first time we run into a jvm bug. This seems to be a hand build JVM and the FreeBSD project doesn't seem to continue maintaining 1.5 JVMs though... hmm maybe we need to go to 1.6 on freebsd though or use 1.5 for compiling. not sure but to use hudson to run multiple jvms we might need to use Linux rather then BSD though. On Sun, Oct 3, 2010 at 4:34 AM, Apache Hudson Server hud...@hudson.apache.org wrote: See https://hudson.apache.org/hudson/job/Lucene-trunk/1313/changes Changes: [rmuir] clear up more compiler warnings [rmuir] clear up more compiler warnings [rmuir] add missing eol-style [rmuir] add missing eol-style [rmuir] clean up some fallthru/deprecation warnings [rmuir] clean up some fallthru/deprecation warnings [rmuir] remove useless casts [rmuir] clear up some easy warnings [rmuir] enable more violations from compile [simonw] LUCENE-2662: Refactored TermsHashPerField to utilize ByteRefHash [uschindler] remove useless maven lib support (is included on hudson's ant) [simonw] LUCENE-2677: Tests failing when run with tests.iter 1 -- [...truncated 14344 lines...] [javadoc] Building index for all the packages and classes... [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/misc/src/java/org/apache/lucene/store/DirectIOLinuxDirectory.java: 44: warning - Tag @link: reference not found: Directory [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build /docs/api/contrib-misc/stylesheet.css... [javadoc] Note: Custom tags that were not seen: @lucene.internal [javadoc] 5 warnings [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build /contrib/misc/lucene-misc-4.0-2010-10-03_02-03-18-javadoc.jar [echo] Building queries... javadocs: [mkdir] Created dir: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build /docs/api/contrib-queries [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package org.apache.lucene.search... [javadoc] Loading source files for package org.apache.lucene.search.regex... [javadoc] Loading source files for package org.apache.lucene.search.similar... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.5.0_16-p9 [javadoc] Building tree for all the packages and classes... [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/JakartaRegexpCapabi lities.java:35: warning - Tag @link: can't find prefix in org.apache.lucene.search.regex.JakartaRegexpCapabilities [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.j ava:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.j ava:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/JavaUtilRegexCapabi lities.java:33: warning - Tag @link: can't find prefix in org.apache.lucene.search.regex.JavaUtilRegexCapabilities [javadoc]
Build failed in Hudson: Solr-trunk #1266
See https://hudson.apache.org/hudson/job/Solr-trunk/1266/changes Changes: [rmuir] clear up more compiler warnings [rmuir] add missing eol-style [rmuir] clean up some fallthru/deprecation warnings [rmuir] remove useless casts [rmuir] enable violations from compile here too [rmuir] clear up some easy warnings [rmuir] enable more violations from compile [simonw] LUCENE-2662: Refactored TermsHashPerField to utilize ByteRefHash [uschindler] remove useless maven lib support (is included on hudson's ant) -- [...truncated 15027 lines...] [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.441 sec [junit] [junit] Testsuite: org.apache.solr.handler.JsonLoaderTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.025 sec [junit] [junit] Testsuite: org.apache.solr.handler.MoreLikeThisHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.843 sec [junit] [junit] Testsuite: org.apache.solr.handler.SpellCheckerRequestHandlerTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.357 sec [junit] [junit] Testsuite: org.apache.solr.handler.StandardRequestHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.669 sec [junit] [junit] Testsuite: org.apache.solr.handler.TestCSVLoader [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.601 sec [junit] [junit] Testsuite: org.apache.solr.handler.TestReplicationHandler [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 23.908 sec [junit] [junit] Testsuite: org.apache.solr.handler.XmlUpdateRequestHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.681 sec [junit] [junit] Testsuite: org.apache.solr.handler.admin.LukeRequestHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.684 sec [junit] [junit] Testsuite: org.apache.solr.handler.admin.SystemInfoHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.003 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.DebugComponentTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.704 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.DistributedSpellCheckComponentTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 8.201 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.DistributedTermsComponentTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.364 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.QueryElevationComponentTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.77 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.SearchHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.713 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.SpellCheckComponentTest [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.917 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.StatsComponentTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.219 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.TermVectorComponentTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.572 sec [junit] [junit] Testsuite: org.apache.solr.handler.component.TermsComponentTest [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 0.613 sec [junit] [junit] Testsuite: org.apache.solr.highlight.FastVectorHighlighterTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.534 sec [junit] [junit] Testsuite: org.apache.solr.highlight.HighlighterConfigTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.462 sec [junit] [junit] Testsuite: org.apache.solr.highlight.HighlighterTest [junit] Tests run: 23, Failures: 0, Errors: 0, Time elapsed: 3.447 sec [junit] [junit] Testsuite: org.apache.solr.request.JSONWriterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.691 sec [junit] [junit] Testsuite: org.apache.solr.request.SimpleFacetsTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 6.65 sec [junit] [junit] Testsuite: org.apache.solr.request.TestBinaryResponseWriter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.634 sec [junit] [junit] Testsuite: org.apache.solr.request.TestFaceting [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 6.274 sec [junit] [junit] Testsuite: org.apache.solr.request.TestWriterPerf [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.923 sec [junit] [junit] Testsuite: org.apache.solr.response.TestCSVResponseWriter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.786 sec
[jira] Resolved: (LUCENE-2663) wrong exception from NativeFSLockFactory (LIA2 test case)
[ https://issues.apache.org/jira/browse/LUCENE-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2663. Resolution: Fixed wrong exception from NativeFSLockFactory (LIA2 test case) - Key: LUCENE-2663 URL: https://issues.apache.org/jira/browse/LUCENE-2663 Project: Lucene - Java Issue Type: Bug Components: Index Reporter: Robert Muir Assignee: Michael McCandless Fix For: 3.1, 4.0 Attachments: LUCENE-2663_test.patch As part of integrating Lucene In Action 2 test cases (LUCENE-2661), I found one of the test cases fail the test is pretty simple, and passes on 3.0. The exception you get instead (LockReleaseFailedException) is pretty confusing and I think we should fix it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Build failed in Hudson: Lucene-trunk #1313
On Sun, Oct 3, 2010 at 10:23 AM, Uwe Schindler u...@thetaphi.de wrote: We have an issue open at infra to enable linprocfs mount in the jail, so we can use the official Linux 32 bit JVMs to build Lucene/Solr (in addition to base_linux package). This may take some time, until then we only have old versions of both 1.6.0_openjdk(unknown bugfixlevel) and 1.5.0_16. Thanks for clarifying uwe! simon - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Simon Willnauer [mailto:simon.willna...@googlemail.com] Sent: Sunday, October 03, 2010 9:33 AM To: dev@lucene.apache.org Subject: Re: Build failed in Hudson: Lucene-trunk #1313 [junit] # [junit] # An unexpected error has been detected by HotSpot Virtual Machine: [junit] # [junit] # SIGSEGV (0xb) at pc=0x0008010c22f2, pid=21897, tid=0xc08ec0 [junit] # [junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_16-p9-root_01_oct_2010_23_12 mixed mode) [junit] # Problematic frame: [junit] # V [libjvm.so+0x2c22f2] [junit] # [junit] # An error report file with more information is saved as hs_err_pid21897.log [junit] # [junit] # If you would like to submit a bug report, please write [junit] # a letter to freebsd-j...@freebsd.org mailing list [junit] # ouch! uwe can we get the error log somehow to figure out if that is a known issue - wouldn't be the first time we run into a jvm bug. This seems to be a hand build JVM and the FreeBSD project doesn't seem to continue maintaining 1.5 JVMs though... hmm maybe we need to go to 1.6 on freebsd though or use 1.5 for compiling. not sure but to use hudson to run multiple jvms we might need to use Linux rather then BSD though. On Sun, Oct 3, 2010 at 4:34 AM, Apache Hudson Server hud...@hudson.apache.org wrote: See https://hudson.apache.org/hudson/job/Lucene-trunk/1313/changes Changes: [rmuir] clear up more compiler warnings [rmuir] clear up more compiler warnings [rmuir] add missing eol-style [rmuir] add missing eol-style [rmuir] clean up some fallthru/deprecation warnings [rmuir] clean up some fallthru/deprecation warnings [rmuir] remove useless casts [rmuir] clear up some easy warnings [rmuir] enable more violations from compile [simonw] LUCENE-2662: Refactored TermsHashPerField to utilize ByteRefHash [uschindler] remove useless maven lib support (is included on hudson's ant) [simonw] LUCENE-2677: Tests failing when run with tests.iter 1 -- [...truncated 14344 lines...] [javadoc] Building index for all the packages and classes... [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/misc/src/java/org/apache/lucene/store/DirectIOLinuxDirectory.java: 44: warning - Tag @link: reference not found: Directory [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build /docs/api/contrib-misc/stylesheet.css... [javadoc] Note: Custom tags that were not seen: �...@lucene.internal [javadoc] 5 warnings [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build /contrib/misc/lucene-misc-4.0-2010-10-03_02-03-18-javadoc.jar [echo] Building queries... javadocs: [mkdir] Created dir: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build /docs/api/contrib-queries [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package org.apache.lucene.search... [javadoc] Loading source files for package org.apache.lucene.search.regex... [javadoc] Loading source files for package org.apache.lucene.search.similar... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.5.0_16-p9 [javadoc] Building tree for all the packages and classes... [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/JakartaRegexpCapabi lities.java:35: warning - Tag @link: can't find prefix in org.apache.lucene.search.regex.JakartaRegexpCapabilities [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.j ava:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/RegexCapabilities.j ava:36: warning - Tag @link: reference not found: RegexTermEnum [javadoc] /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/contr ib/queries/src/java/org/apache/lucene/search/regex/JavaUtilRegexCapabi lities.java:33: warning - Tag @link: can't find prefix in
[jira] Updated: (LUCENE-2682) create test case to verify we support 2.1B terms
[ https://issues.apache.org/jira/browse/LUCENE-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2682: --- Attachment: LUCENE-2682.patch create test case to verify we support 2.1B terms -- Key: LUCENE-2682 URL: https://issues.apache.org/jira/browse/LUCENE-2682 Project: Lucene - Java Issue Type: Improvement Components: Index Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 3.1, 4.0 Attachments: LUCENE-2682.patch I created a test case for this... I'm leaving it as @Ignore because it takes more than four hours on a faaast machine (beast) to run. I think we should run this before each release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Created: (LUCENE-2682) create test case to verify we support 2.1B terms
create test case to verify we support 2.1B terms -- Key: LUCENE-2682 URL: https://issues.apache.org/jira/browse/LUCENE-2682 Project: Lucene - Java Issue Type: Improvement Components: Index Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 3.1, 4.0 Attachments: LUCENE-2682.patch I created a test case for this... I'm leaving it as @Ignore because it takes more than four hours on a faaast machine (beast) to run. I think we should run this before each release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
RE: svn commit: r1003954 - /lucene/dev/trunk/lucene/contrib/contrib-build.xml
Ha, thanks. Nice catch! I was always wondering why Javadocs creation sometimes
prints thousands of warnings for some contribs!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: rm...@apache.org [mailto:rm...@apache.org]
Sent: Sunday, October 03, 2010 2:19 PM
To: comm...@lucene.apache.org
Subject: svn commit: r1003954 - /lucene/dev/trunk/lucene/contrib/contrib-
build.xml
Author: rmuir
Date: Sun Oct 3 12:18:33 2010
New Revision: 1003954
URL: http://svn.apache.org/viewvc?rev=1003954view=rev
Log:
add dependency to prevent javadocs warnings/errors
Modified:
lucene/dev/trunk/lucene/contrib/contrib-build.xml
Modified: lucene/dev/trunk/lucene/contrib/contrib-build.xml
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/contrib/contrib-
build.xml?rev=1003954r1=1003953r2=1003954view=diff
==
--- lucene/dev/trunk/lucene/contrib/contrib-build.xml (original)
+++ lucene/dev/trunk/lucene/contrib/contrib-build.xml Sun Oct 3 12:18:33
2010
@@ -86,7 +86,7 @@
/sequential
/target
- target name=javadocs
+ target name=javadocs depends=compile-core
sequential
mkdir dir=${javadoc.dir}/contrib-${name}/
invoke-javadoc
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2681) fix generics violations in contrib/modules
[ https://issues.apache.org/jira/browse/LUCENE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917350#action_12917350 ] Robert Muir commented on LUCENE-2681: - the policeman informed me the patch is ok, so i will commit it, but there are more generics problems in contrib/queryparser... fix generics violations in contrib/modules -- Key: LUCENE-2681 URL: https://issues.apache.org/jira/browse/LUCENE-2681 Project: Lucene - Java Issue Type: Bug Components: contrib/*, contrib/analyzers Affects Versions: 3.1, 4.0 Reporter: Robert Muir Fix For: 3.1, 4.0 Attachments: LUCENE-2681_contrib.patch, LUCENE-2681_modules.patch There are some generics violations... we should fix them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2662) BytesHash
[ https://issues.apache.org/jira/browse/LUCENE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917354#action_12917354 ] Jason Rutherglen commented on LUCENE-2662: -- Simon, I'm going to get deletes working, tests passing using maps in the RT branch, then we can integrate. This'll probably be best. BytesHash - Key: LUCENE-2662 URL: https://issues.apache.org/jira/browse/LUCENE-2662 Project: Lucene - Java Issue Type: Improvement Components: Index Affects Versions: Realtime Branch, 4.0 Reporter: Jason Rutherglen Assignee: Simon Willnauer Priority: Minor Fix For: Realtime Branch, 4.0 Attachments: LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch This issue will have the BytesHash separated out from LUCENE-2186 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Resolved: (LUCENE-2681) fix generics violations in contrib/modules
[ https://issues.apache.org/jira/browse/LUCENE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-2681. - Resolution: Fixed the queryparser warnings were trivial, just raw types that needed to be generified: see revision 1003990. fix generics violations in contrib/modules -- Key: LUCENE-2681 URL: https://issues.apache.org/jira/browse/LUCENE-2681 Project: Lucene - Java Issue Type: Bug Components: contrib/*, contrib/analyzers Affects Versions: 3.1, 4.0 Reporter: Robert Muir Fix For: 3.1, 4.0 Attachments: LUCENE-2681_contrib.patch, LUCENE-2681_modules.patch There are some generics violations... we should fix them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2657:
Attachment: LUCENE-2657.patch
First cut at Maven POMs for Lucene and Solr.
The following script, which installs non-mavenized artifacts into the user's
local Maven repository, must be run before the Maven build works:
{code}
mvn install:install-file -DgroupId=com.ibm.icu -DartifactId=icu4j
-Dversion=4.4 -Dpackaging=jar -Dfile=modules/analysis/icu/lib/icu4j-4_4.jar
mvn install:install-file -DgroupId=xerces -DartifactId=xercesImpl
-Dversion=2.9.1-patched-XERCESJ-1257 -Dpackaging=jar
-Dfile=lucene/contrib/benchmark/lib/xerces-2.9.1-patched-XERCESJ-1257.jar
mvn install:install-file -DgroupId=com.sleepycat -DartifactId=berkeleydb
-Dversion=4.7.25 -Dpackaging=jar -Dfile=lucene/contrib/db/bdb/lib/db-4.7.25.jar
mvn install:install-file -DgroupId=com.sleepycat -DartifactId=berkeleydb-je
-Dversion=3.3.93 -Dpackaging=jar
-Dfile=lucene/contrib/db/bdb-je/lib/je-3.3.93.jar
mvn install:install-file -DgroupId=org.apache.solr
-DartifactId=solr-commons-csv -Dversion=4.0-SNAPSHOT -Dpackaging=jar
-Dfile=solr/lib/commons-csv-1.0-SNAPSHOT-r966014.jar
mvn install:install-file -DgroupId=org.apache.solr -DartifactId=solr-noggit
-Dversion=r944541 -Dpackaging=jar -Dfile=solr/lib/apache-solr-noggit-r944541.jar
mvn install:install-file -DgroupId=org.apache.tika -DartifactId=tika-core
-Dversion=0.8-SNAPSHOT -Dpackaging=jar
-Dfile=solr/contrib/extraction/lib/tika-core-0.8-SNAPSHOT.jar
jar xvf solr/contrib/extraction/lib/tika-parsers-0.8-SNAPSHOT.jar
META-INF/maven/org.apache.tika/tika-parsers/pom.xml
mvn install:install-file
-Dfile=solr/contrib/extraction/lib/tika-parsers-0.8-SNAPSHOT.jar
-DpomFile=META-INF/maven/org.apache.tika/tika-parsers/pom.xml
rm -rf META-INF
{code}
Everything compiles (using {{mvn -DskipTests clean install}}). Except for two
Solr tests, all tests pass. The two tests that fail for me (on Win Vista 64,
Sun JDK 1.6.0_13) are: JettyWebAppTest and Solr Cell's
ExtractingRequestHandlerTest.testArabicPDF().
I have added configurations for running appassembler-maven-plugin (to produce
run-time windows and linux scripts with lib/ dirs containing dependencies) for
all classes with main() functions that are intended as tools rather than static
tests.
I haven't tried using the POMs as project configuration for IntelliJ, so I'm
not sure how that will go.
This is a work-in-progress. Please test and let me know if you find problems,
or would like to see more stuff added, or if you think the design is all wrong.
One challenge worth noting is that Maven disallows aggregator POMs (those with
a {{modules}} section directing nested Maven invocations) from producing any
artifacts other than the POM itself. As a result, the 4 or 5 locations in the
Lucene/Solr build that have mixed content (to borrow the XML term for mixed
nested element and text content) have to be fudged; e.g. the Lucene and Solr
core POMs are located in {{lucene/src/}} and {{solr/src/}}, because the
aggregator POMs at {{lucene/}} and {{solr/}} can't produce binary artifacts.
(The conventional Maven way to address this kind of issue is to make the core
modules be siblings of the nested modules.)
Replace Maven POM templates with full POMs, and change documentation
accordingly
Key: LUCENE-2657
URL: https://issues.apache.org/jira/browse/LUCENE-2657
Project: Lucene - Java
Issue Type: Improvement
Components: Build
Reporter: Steven Rowe
Assignee: Steven Rowe
Fix For: 3.1, 4.0
Attachments: LUCENE-2657.patch
The current Maven POM templates only contain dependency information, the bare
bones necessary for uploading artifacts to the Maven repository.
Full Maven POMs will include the information necessary to run a multi-module
Maven build, in addition to serving the same purpose as the current POM
templates.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Created: (LUCENE-2683) upgrade icu libraries to 4.4.2
upgrade icu libraries to 4.4.2 -- Key: LUCENE-2683 URL: https://issues.apache.org/jira/browse/LUCENE-2683 Project: Lucene - Java Issue Type: Improvement Reporter: Robert Muir Priority: Minor modules/analysis uses 4.4 solr/contrib/extraction uses 4.2.1 I think we should keep them the same version, for consistency, and go to 4.4.2 since it has bugfixes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
[ https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917368#action_12917368 ] Robert Muir commented on LUCENE-2657: - bq. Except for two Solr tests, all tests pass. The two tests that fail for me (on Win Vista 64, Sun JDK 1.6.0_13) are: JettyWebAppTest and Solr Cell's ExtractingRequestHandlerTest.testArabicPDF(). maybe it is an icu classpath issue. modules/analysis and solr/contrib/extraction both use different, out of date versions. i opened LUCENE-2683 Replace Maven POM templates with full POMs, and change documentation accordingly Key: LUCENE-2657 URL: https://issues.apache.org/jira/browse/LUCENE-2657 Project: Lucene - Java Issue Type: Improvement Components: Build Reporter: Steven Rowe Assignee: Steven Rowe Fix For: 3.1, 4.0 Attachments: LUCENE-2657.patch The current Maven POM templates only contain dependency information, the bare bones necessary for uploading artifacts to the Maven repository. Full Maven POMs will include the information necessary to run a multi-module Maven build, in addition to serving the same purpose as the current POM templates. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2683) upgrade icu libraries to 4.4.2
[ https://issues.apache.org/jira/browse/LUCENE-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2683: Attachment: LUCENE-2683.patch all tests pass upgrading icu in both places. upgrade icu libraries to 4.4.2 -- Key: LUCENE-2683 URL: https://issues.apache.org/jira/browse/LUCENE-2683 Project: Lucene - Java Issue Type: Improvement Affects Versions: 3.1, 4.0 Reporter: Robert Muir Priority: Minor Fix For: 3.1, 4.0 Attachments: LUCENE-2683.patch modules/analysis uses 4.4 solr/contrib/extraction uses 4.2.1 I think we should keep them the same version, for consistency, and go to 4.4.2 since it has bugfixes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2683) upgrade icu libraries to 4.4.2
[ https://issues.apache.org/jira/browse/LUCENE-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2683: Assignee: Robert Muir Fix Version/s: 3.1 4.0 Affects Version/s: 3.1 4.0 upgrade icu libraries to 4.4.2 -- Key: LUCENE-2683 URL: https://issues.apache.org/jira/browse/LUCENE-2683 Project: Lucene - Java Issue Type: Improvement Affects Versions: 3.1, 4.0 Reporter: Robert Muir Assignee: Robert Muir Priority: Minor Fix For: 3.1, 4.0 Attachments: LUCENE-2683.patch modules/analysis uses 4.4 solr/contrib/extraction uses 4.2.1 I think we should keep them the same version, for consistency, and go to 4.4.2 since it has bugfixes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2662) BytesHash
[ https://issues.apache.org/jira/browse/LUCENE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917372#action_12917372 ] Simon Willnauer commented on LUCENE-2662: - bq. Simon, I'm going to get deletes working, tests passing using maps in the RT branch, then we can integrate. This'll probably be best. Jason, I suggest you create a separate issue something like Integrate BytesRefHash in Realtime Branch and I will take care of it. I think this issue had a clear target to factor out the hash table out of TermsHashPerField and we should close it. lets use a new one to track the integration. Thoughts? Simon BytesHash - Key: LUCENE-2662 URL: https://issues.apache.org/jira/browse/LUCENE-2662 Project: Lucene - Java Issue Type: Improvement Components: Index Affects Versions: Realtime Branch, 4.0 Reporter: Jason Rutherglen Assignee: Simon Willnauer Priority: Minor Fix For: Realtime Branch, 4.0 Attachments: LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch This issue will have the BytesHash separated out from LUCENE-2186 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2682) create test case to verify we support 2.1B terms
[
https://issues.apache.org/jira/browse/LUCENE-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917382#action_12917382
]
Robert Muir commented on LUCENE-2682:
-
in MyTermAttributeImpl:
{code}
public int toBytesRef(BytesRef bs) {
bs.copy(bytes);
{code}
i don't think you need to copy bytes? maybe it saves a whole 30 seconds in your
4 hour test time :)
i did a shallow-copy with collation.
create test case to verify we support 2.1B terms
--
Key: LUCENE-2682
URL: https://issues.apache.org/jira/browse/LUCENE-2682
Project: Lucene - Java
Issue Type: Improvement
Components: Index
Reporter: Michael McCandless
Assignee: Michael McCandless
Fix For: 3.1, 4.0
Attachments: LUCENE-2682.patch
I created a test case for this... I'm leaving it as @Ignore because it takes
more than four hours on a faaast machine (beast) to run. I think we should
run this before each release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2662) BytesHash
[ https://issues.apache.org/jira/browse/LUCENE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-2662: - Affects Version/s: (was: Realtime Branch) Fix Version/s: (was: Realtime Branch) BytesHash - Key: LUCENE-2662 URL: https://issues.apache.org/jira/browse/LUCENE-2662 Project: Lucene - Java Issue Type: Improvement Components: Index Affects Versions: 4.0 Reporter: Jason Rutherglen Assignee: Simon Willnauer Priority: Minor Fix For: 4.0 Attachments: LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch This issue will have the BytesHash separated out from LUCENE-2186 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2662) BytesHash
[ https://issues.apache.org/jira/browse/LUCENE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917416#action_12917416 ] Jason Rutherglen commented on LUCENE-2662: -- Lets commit this to trunk. We need to merge in all of trunk to the RT branch, or vice versa at some point anyways. This patch could be a part of that bulk merge-in, or we can simply do it now. BytesHash - Key: LUCENE-2662 URL: https://issues.apache.org/jira/browse/LUCENE-2662 Project: Lucene - Java Issue Type: Improvement Components: Index Affects Versions: 4.0 Reporter: Jason Rutherglen Assignee: Simon Willnauer Priority: Minor Fix For: 4.0 Attachments: LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch, LUCENE-2662.patch This issue will have the BytesHash separated out from LUCENE-2186 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
[ https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917438#action_12917438 ] Chris Male commented on LUCENE-2657: Hi Steven, bq. The following script, which installs non-mavenized artifacts into the user's local Maven repository Would system scope dependencies be an alternative way? Then we can specify the systemPath to where the jars are in the lib folders. Reason I suggest this is that if someone replaces one of those jar (which will happen I'm sure) or simply adds another, then we cannot simply update the appropriate pom. We'd also need to install the jars locally (possibly again). Replace Maven POM templates with full POMs, and change documentation accordingly Key: LUCENE-2657 URL: https://issues.apache.org/jira/browse/LUCENE-2657 Project: Lucene - Java Issue Type: Improvement Components: Build Affects Versions: 3.1, 4.0 Reporter: Steven Rowe Assignee: Steven Rowe Fix For: 3.1, 4.0 Attachments: LUCENE-2657.patch The current Maven POM templates only contain dependency information, the bare bones necessary for uploading artifacts to the Maven repository. Full Maven POMs will include the information necessary to run a multi-module Maven build, in addition to serving the same purpose as the current POM templates. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
[ https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917448#action_12917448 ] Steven Rowe commented on LUCENE-2657: - bq. Would system scope dependencies be an alternative way? I thought of that, and it probably makes sense for most of them. But a jar like tika-parsers-0.8-SNAPSHOT.jar, with 10 or 15 dependencies, would be even messier to deal with as a system dependency than as a locally installed artifact. We would have to go look at the POM for it (contained conveniently within the jar, as it happens), compare the dependencies against the versions of the local dependencies (which would have previously had to be transferred to the both the Solr Cell and the DIH Extras POMs) and make changes in both places. Replace Maven POM templates with full POMs, and change documentation accordingly Key: LUCENE-2657 URL: https://issues.apache.org/jira/browse/LUCENE-2657 Project: Lucene - Java Issue Type: Improvement Components: Build Affects Versions: 3.1, 4.0 Reporter: Steven Rowe Assignee: Steven Rowe Fix For: 3.1, 4.0 Attachments: LUCENE-2657.patch The current Maven POM templates only contain dependency information, the bare bones necessary for uploading artifacts to the Maven repository. Full Maven POMs will include the information necessary to run a multi-module Maven build, in addition to serving the same purpose as the current POM templates. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Build failed in Hudson: Lucene-trunk #1314
See https://hudson.apache.org/hudson/job/Lucene-trunk/1314/changes Changes: [rmuir] clear up more warnings in modules/contrib [rmuir] clear up more warnings in modules/contrib [rmuir] LUCENE-2681: fix generics violations in contrib/modules [rmuir] LUCENE-2681: fix generics violations in contrib/modules [rmuir] clear up javadocs warnings/errors (forgot to svn add these overview.htmls) [rmuir] clear up javadocs warnings/errors (forgot to svn add these overview.htmls) [rmuir] clear up javadocs warnings/errors [rmuir] clear up javadocs warnings/errors [rmuir] add dependency to prevent javadocs warnings/errors [mikemccand] LUCENE-2663: move trunk CHANGES entry under 3.x [mikemccand] LUCENE-2663: don't try to clear prior lock in IndexWriter when create=true -- [...truncated 14461 lines...] [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-remote/stylesheet.css... [javadoc] Note: Custom tags that were not seen: @lucene.experimental, @lucene.internal [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/contrib/remote/lucene-remote-4.0-2010-10-04_02-03-18-javadoc.jar [echo] Building spatial... build-queries: common.init: build-lucene: init: clover.setup: clover.info: clover: common.compile-core: compile-core: javadocs: [mkdir] Created dir: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-spatial [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package org.apache.lucene.spatial... [javadoc] Loading source files for package org.apache.lucene.spatial.geohash... [javadoc] Loading source files for package org.apache.lucene.spatial.geometry... [javadoc] Loading source files for package org.apache.lucene.spatial.geometry.shape... [javadoc] Loading source files for package org.apache.lucene.spatial.tier... [javadoc] Loading source files for package org.apache.lucene.spatial.tier.projections... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.5.0_16-p9 [javadoc] Building tree for all the packages and classes... [javadoc] Building index for all the packages and classes... [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-spatial/stylesheet.css... [javadoc] Note: Custom tags that were not seen: @lucene.experimental, @lucene.internal [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/contrib/spatial/lucene-spatial-4.0-2010-10-04_02-03-18-javadoc.jar [echo] Building spellchecker... compile-analyzers-common: common.init: build-lucene: init: clover.setup: clover.info: clover: common.compile-core: compile-core: javadocs: [mkdir] Created dir: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-spellchecker [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package org.apache.lucene.search.spell... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.5.0_16-p9 [javadoc] Building tree for all the packages and classes... [javadoc] Building index for all the packages and classes... [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-spellchecker/stylesheet.css... [javadoc] Note: Custom tags that were not seen: @lucene.internal [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/contrib/spellchecker/lucene-spellchecker-4.0-2010-10-04_02-03-18-javadoc.jar [echo] Building swing... compile-analyzers-common: common.init: build-lucene: init: clover.setup: clover.info: clover: common.compile-core: compile-core: javadocs: [mkdir] Created dir: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-swing [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package org.apache.lucene.swing.models... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.5.0_16-p9 [javadoc] Building tree for all the packages and classes... [javadoc] Building index for all the packages and classes... [javadoc] Building index for all classes... [javadoc] Generating /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/docs/api/contrib-swing/stylesheet.css... [javadoc] Note: Custom tags that were not seen: @lucene.experimental, @lucene.internal [jar] Building jar: /usrhttps://hudson.apache.org/hudson/job/Lucene-trunk/ws/lucene/build/contrib/swing/lucene-swing-4.0-2010-10-04_02-03-18-javadoc.jar
Re: FW: Solr and LCF security at query time
www.openldap.org Haven't used it. Here's the License: http://www.openldap.org/software/release/license.html karl.wri...@nokia.com wrote: Looking around for no-Apache java-only solutions to the AD authentication problem, it seems to me that what we mainly have available is JAAS plus the following JAAS login module: com.sun.security.auth.module.Krb5LoginModule ... which should permit AD authentication to take place, if properly configured. So, we *could* stipulate that the search component receive credentials, somehow, upon being called, and then authenticate each time. (There's a ticket cache involved, so this is not as insane as it sounds). But this architecture option makes me twitchy because I am unclear how exactly this would help Tomcat interact with the browser to manage signon for a web application. So it might be better to push the authentication itself upstream into a module meant to be plugged into Tomcat, and have Solr just receive and deal with the resulting ticket, and/or an authenticated, domain-qualified user name. The task of the LCF Solr search component or filter would then be to do the following: (1) Get hold of the ticket/authenticated user name, which will probably come in as some attribute to the search that's presented to Solr. (Someone needs to specify what this attribute is called still). (2) Invoke a configured LCF authority service with that user name, via http, and get back a list of access tokens for the user (3) Form the search expression with the user's access tokens (if it's a search component), or filter the results using those access tokens (if it's a filter), remembering that every document that's participating in security should have __ACCESS_TOKEN__document and __DENY_TOKEN__document metadata I've also been pondering whether which we should build: a search component or filter? I think there are advantages to both, so I think we should build both, and let people use what they need. I think the technical aspects of building the Solr component are well understood by this group, so the only open issue remains how to build a JAAS-based AD authentication module for tomcat that would do what we needed. I'll be doing more research as time permits... Karl From: Wright Karl (Nokia-S/Cambridge) Sent: Wednesday, April 21, 2010 8:02 PM To: connectors-u...@incubator.apache.org; lucene-...@apache.org; connectors-...@incubator.apache.org Subject: RE: FW: Solr and LCF security at query time Hi Peter, I just committed the promised changes to the LCF Solr output connector. ACL metadata will now be posted to the Solr Http interface along with the document as the two following fields: __ACCESS_TOKEN__document __DENY_TOKEN__document There will, of course, potentially be multiple values for each of these two fields. Hope this helps, Karl From: ext Peter Sturge [mailto:peter.stu...@googlemail.com] Sent: Tuesday, April 20, 2010 6:51 PM To: connectors-u...@incubator.apache.org Subject: Re: FW: Solr and LCF security at query time Hi Karl, Thanks for the info. I'll have a look at the link and try to take in as much sugar as my insulin levels will handle... It sounds like the necessary interface(s) are already in LCF - just a matter of implementing them in the Solr 1872 plugin. I'll need to digest the LCF stuff to get to grips with it..please bear with me while I do that... When you say: The LCF solr output connection doesn't yet do this, but it is trivial for me to make that happen. Do you mean a mechanism by which solr.war can get url et al info from its parent container (Tomcat, Jetty etc.), or have I misinterpreted this? Thanks, Peter On Tue, Apr 20, 2010 at 11:05 PM,karl.wri...@nokia.commailto:karl.wri...@nokia.com wrote: Hi Peter, I'm the principal committer for LCF, but I don't know as much about Solr as I ought to, so it sounds like a potentially productive collaboration. LCF does exactly what you are looking for - the only issue at all is that you need to fetch a URL from a webapp to get what you are looking for. The plugs are all inside LCF for different kinds of repositories. Here's a link that might help with drinking the LCF koolaid, as it were: https://cwiki.apache.org/confluence/display/CONNECTORS/Lucene+Connectors+Framework+concepts The url would be something like this (on a locally installed tomcat-based LCF instance): http://localhost:8080/lcf-authority-service/useracls?username=someusern...@somedomain.com ... and this fetch returns something like: TOKEN:xxx TOKEN:yyy TOKEN:zzz ... which represent the amalgamated tokens for all of the defined authorities, and by some strange coincidence ( ;-) ) are compatible with certain pieces of metadata that have been passed into Solr with each document - one set of Allow tokens, and a second set of Deny tokens. The LCF solr output connection doesn't yet do this,
