Re: Welcome Alan Woodward as Lucene/Solr committer

Welcome Alan! Alan Woodward wrote: Thanks Robert. I'm a developer based in Cambridge, UK, and have been working on search engines for 10 years or so. Up until a couple of years ago I was mainly using closed-source implementations, and discovering lucene/solr was a breath of fresh air (you

RE: VOTE: release 4.0 (RC2)

+1 The smoke tester succeeded for me on Win7+Cygwin and on OS X 10.8.2, using Oracle Java 1.6.0_35 and 1.7.0_07 on both OSs. Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Saturday, October 06, 2012 4:11 AM To: dev@lucene.apache.org Subject: VOTE: release 4.

RE: [DISCUSS] TM in website graphic images

scussing before moving to the vote - but this is my response to "Thoughts?". My personal opinion, so FWIW. - Mark On 09/28/2012 09:11 AM, Steven A Rowe wrote: > I did a survey of the 184 ASF projects listed on this page: > <http://projects.apache.org/indexes/alpha.html>

RE: [DISCUSS] TM in website graphic images

PM To: dev@lucene.apache.org Subject: Re: [DISCUSS] TM in website graphic images On Thu, Sep 27, 2012 at 7:59 PM, Steven A Rowe wrote: > ... ensure that it > includes a small "TM" symbol in the graphic or > immediately adjacent to it. For pages that include the

[DISCUSS] TM in website graphic images

I want to finish addressing the Project Branding Requirements at . One of the outstanding issues is stamping our graphics with "TM". From : Logos are important to recognize as

RE: VOTE: release 4.0 (take two)

+1: smoker admitted SUCCESS! on Win7+Cygwin -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Thursday, September 27, 2012 3:16 PM To: dev@lucene.apache.org Subject: VOTE: release 4.0 (take two) artifacts are here: http://s.apache.org/lusolr40rc1 By the way, thanks fo

RE: svn commit: r1390535 - in /lucene/dev/branches/branch_4x: ./ dev-tools/ dev-tools/scripts/smokeTestRelease.py

xe=python3 to my ant command. But I'm wondering if there is anything special cleanup I need to do such as I had to do when running the py file directly. -- Jack Krupansky -Original Message- From: Steven A Rowe Sent: Wednesday, September 26, 2012 1:03 PM To: dev@lucene.apache.org Subj

RE: svn commit: r1390535 - in /lucene/dev/branches/branch_4x: ./ dev-tools/ dev-tools/scripts/smokeTestRelease.py

We should change the ant target to use the environment variables if they exist. In the mean time, Jack, just add the following to your ant cmdline: -DJAVA6_HOME="$JAVA6_HOME" -DJAVA7_HOME="$JAVA7_HOME" Steve -Original Message- From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Wedne

RE: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193

+1 -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Wednesday, September 26, 2012 6:22 AM To: dev@lucene.apache.org Subject: Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193 Can we improve the way the smoketester works here? I've been running lucene's te

RE: Smoke test instructions

Jack, I think Python 3.2 is required. if you run it like "python3.2 –u dev-tools/scripts/smokeTestRelease.py", it will give cmdline help. Steve From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Tuesday, September 25, 2012 12:01 PM To: Lucene/Solr Dev Subject: Smoke test instructions

RE: VOTE: release 4.0

nday, September 24, 2012 2:32 PM To: dev@lucene.apache.org Subject: Re: VOTE: release 4.0 On Mon, Sep 24, 2012 at 2:26 PM, Steven A Rowe wrote: > Running smokeTestRelease.py on Win7+Cygwin, I can't get past the Solr example > test under Java7. > I'm not really sure thats a re

RE: VOTE: release 4.0

Running smokeTestRelease.py on Win7+Cygwin, I can't get past the Solr example test under Java7. I ran the smoke tester three times using Oracle v1.7.0_01 64-bit, and then two times using Oracle v1.7.0_07 64-bit. Four out of the five runs failed on the first Java7 Solr example test (from the un

RE: Re:VOTE: release 4.0

Hello秋水, Rather than complaining about the javadocs, perhaps you could help by pointing out specific problems? Or even better, create JIRA issues and provide patches: http://wiki.apache.org/lucene-java/HowToContribute Steve From: 秋水 [mailto:sdrkyj_luc...@163.com] Sent: Monday, September 24, 2

RE: svn commit: r1388844 - /lucene/dev/branches/lucene_solr_4_0/dev-tools/scripts/smokeTestRelease.py

Thanks Mike, I switched to properly populating POMtemplates, and removed the debug printing. Committed to the release branch, branch_4x, and trunk. I also enabled running the smoke tester under Cygwin again. It passed for me using the 'ant nightly-smoke'-produced fake release. Steve -Or

RE: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #3

ase branch and runs > 'ant nightly-smoke -DJAVA6_HOME= -DJAVA7_HOME=' > > On Sat, Sep 22, 2012 at 11:29 AM, Steven A Rowe wrote: >> The maven checks use python XML parsing, which appears to be complaining >> about well-formedness of a POM file. >> >

RE: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #3

nt nightly-smoke -DJAVA6_HOME= -DJAVA7_HOME=' > > On Sat, Sep 22, 2012 at 11:29 AM, Steven A Rowe wrote: >> The maven checks use python XML parsing, which appears to be complaining >> about well-formedness of a POM file. >> >> How is smoketester being run

RE: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #3

The maven checks use python XML parsing, which appears to be complaining about well-formedness of a POM file. How is smoketester being run? Against a file:// url built locally? Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Saturday, September 22, 2012 11:

RE: Can the build failure subject line say which modules had failures?

The Jenkins Email-ext plugin allows "content tokens" - dynamically interpolated build information - to be included in the generated email subject as well as the body, so assuming there is a way to extract the names of failed modules from the build log, this should be possible. I'm hesitant to

RE: being a good citizen is hard when you can't successfully run tests....

I always run both Lucene and Solr tests. Yes, Solr tests are more likely to fail than Lucene tests. When that happens, I see if I can repro with the same seed (almost never works), then run the remaining modules' tests. Related question: how hard would it be to set up Ant testing to be like th

RE: SonaType repo in Maven POMs

dtesting-runner, so there is nothing to fix. The svn history shows that pre-LUCENE-4365, there was a dependency from lucene-core POM on randomizedtesting-runner, but I removed that as part of LUCENE-4365. Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Friday

RE: SonaType repo in Maven POMs

, but I removed that as part of LUCENE-4365. Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Friday, September 07, 2012 8:21 AM To: dev@lucene.apache.org Subject: RE: SonaType repo in Maven POMs About the lucene-core POM inclusion of the sonatype repo, I found

RE: SonaType repo in Maven POMs

Agreed. FYI, my resistence to declaring the sonatype repo in the top-level POM is twofold: 1) It will slow down the build, since *every* missing dependency will cause the sonatype repo to be checked before Maven Central. 2) Given evidence that resolution from the sonatype repo *sometimes* wor

RE: SonaType repo in Maven POMs

--Original Message----- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Friday, September 07, 2012 8:00 AM To: dev@lucene.apache.org Subject: RE: SonaType repo in Maven POMs Hi Dawid, What issue will be fixed by adding sonatype to the master pom? FYI, I've successfully run the maven

RE: SonaType repo in Maven POMs

See my last post - sonatype repo is being used from lucene test-framework using the current configuration. -Original Message- From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid Weiss Sent: Friday, September 07, 2012 8:08 AM To: dev@lucene.apache.org Subject: Re

RE: SonaType repo in Maven POMs

I think the sonatype repo was just acting flaky. Just now I rm -rf'd com/carrotsearch/randomizedtesting/ from my local repo, and I see this when I run 'mvn -DskipTests install' from the top level: --- [INFO] Building Lucene Test Framework [INFO]task-segment: [install] [INFO]

RE: SonaType repo in Maven POMs

Hi Dawid, What issue will be fixed by adding sonatype to the master pom? FYI, I've successfully run the maven build from both trunk and branch_4x on my box since you upgraded, including downloading randomizedtesting-runner-2.0.0.jar. I'm not sure why the randomizedtesting jar is referenced fro

RE: svn commit: r1381812 - in /lucene/dev/trunk/dev-tools/maven: lucene/codecs/src/test/pom.xml.template lucene/core/src/test/pom.xml.template solr/core/src/test/pom.xml.template solr/solrj/src/test/p

Thanks Robert. -Original Message- From: rm...@apache.org [mailto:rm...@apache.org] Sent: Thursday, September 06, 2012 8:10 PM To: comm...@lucene.apache.org Subject: svn commit: r1381812 - in /lucene/dev/trunk/dev-tools/maven: lucene/codecs/src/test/pom.xml.template lucene/core/src/test/p

RE: JIRA assign issue

Hi Jacek, I've just added you to the Contributors group for the Solr project on JIRA. This should allow you to assign issues to yourself. Steve -Original Message- From: Jacek Plebanek [mailto:pleba...@gmail.com] Sent: Thursday, September 06, 2012 8:32 AM To: dev@lucene.apache.org Subj

RE: [jira] [Commented] (LUCENE-4362) ban tab-indented source

ented source I took care of it. THe problem was 2 Erick Ericksons. one was erick.erick...@gmail.com (that one had permissions), but that either isn't you, or was an old address. I put your new one in there and disabled access for the other one On Wed, Sep 5, 2012 at 12:59 PM, Steven A Rowe w

RE: [jira] [Commented] (LUCENE-4362) ban tab-indented source

Hi Erick, I think I can add you to the appropriate group. Trying now. Steve -Original Message- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Wednesday, September 05, 2012 12:56 PM To: dev@lucene.apache.org Subject: Re: [jira] [Commented] (LUCENE-4362) ban tab-indented sou

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #87: POMs out of sync

Hi Dawid, I'm pretty sure Uwe's wrong about that - e.g., it's possible to build projects from zero downloaded dependencies. The sonatype repo declaration in the test-framework POM doesn't give an updatePolicy for releases, so the default policy, daily, is used. I think the updatePolicy is con

RE: [JENKINS] Lucene-Solr-4.x-Linux (64bit/ibm-j9-jdk7) - Build # 752 - Failure!

will investigate this later today. Thanks Steve. > > Sent from mobile phone. > > On Aug 30, 2012 5:18 PM, "Steven A Rowe" wrote: >> >> There is a strange failure here in collecting test results (excerpted >> below) - parsing of XML test output fails because th

RE: [JENKINS] Lucene-Solr-4.x-Linux (64bit/ibm-j9-jdk7) - Build # 752 - Failure!

Will do. - Steve -Original Message- From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid Weiss Sent: Thursday, August 30, 2012 4:34 PM To: dev@lucene.apache.org Subject: Re: [JENKINS] Lucene-Solr-4.x-Linux (64bit/ibm-j9-jdk7) - Build # 752 - Failure! > 114:

RE: large messages from Jenkins failures

rver a little less than an hour before this post, with subject "[JENKINS] Lucene-Solr-trunk-Windows (32bit/jdk1.7.0_06) - Build # 533 - Failure!". I chose the 200K chars limit somewhat arbitrarily - please let me know if you think it should be different. Steve -Original Mess

RE: [JENKINS] Lucene-Solr-4.x-Linux (64bit/ibm-j9-jdk7) - Build # 752 - Failure!

There is a strange failure here in collecting test results (excerpted below) - parsing of XML test output fails because there are missing closing angle brackets on the last few elements in the file

RE: Build failed in Jenkins: Lucene-trunk-Linux-Java7-64-test-only #3430

Simon has granted me access on flonkings Jenkins, and I've set up the hugerriblific build failure regex in the notification email configuration for the jobs hosted there. - Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Saturday, August 25, 2012 8:13

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #64: POMs out of sync

On August 12th, roughly the same day BasicDistributedZkTest#testDistribSearch started failing regularly under the Maven builds, I reduced Solr log output under the Maven builds, because Jenkins wasn't sending any notification emails when the Maven builds failed, AFAICT because the voluminous Sol

RE: large messages from Jenkins failures

Actually, after discussing with Uwe on #lucene-dev IRC, I'm looking into another mechanism to reduce the size of email messages: the Jenkins Email-Ext plugin has a per-build-job configuration item named "Pre-send script" that allows you to modify the MimeMessage object representing an email via

RE: large messages from Jenkins failures

this would be reasonable, I'm willing to (try to) do the work. Steve -Original Message----- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Monday, August 20, 2012 4:10 PM To: dev@lucene.apache.org Subject: RE: large messages from Jenkins failures +1 to using -Dtests.showOutput=ne

RE: Problems with ivy resolution

Hi Lance, I don't see any freezing problems at all. icu4j-v49.1 downloads fine for me. I live in New York State in the US. Maybe the trouble your'e having has something to do with your location? (By the way, "ant compile" under lucene/ doesn't enter analysis/icu/.) Steve -Original Mess

RE: Build failed in Jenkins: Lucene-trunk-Linux-Java7-64-test-only #3430

I'm pretty sure the AMBFR isn't being using on flonkings. I don't have access, so I haven't put it there. - Steve -Original Message- From: Michael McCandless [mailto:luc...@mikemccandless.com] Sent: Saturday, August 25, 2012 6:12 PM To: dev@lucene.apache.org Cc: buil...@flonkings.com; s

RE: Maven and IntelliJ (but not Ant) compilation fails on branch_4x and trunk using Java6; Java7 works for all

; http://blog.mikemccandless.com > > On Wed, Aug 22, 2012 at 6:13 PM, Yonik Seeley wrote: >> On Wed, Aug 22, 2012 at 4:24 PM, Steven A Rowe wrote: >>> On Win7, I'm getting compilation failures on branch_4x and trunk, under >>> Maven (2.2.1 and 3.0.4) and Intel

RE: Maven and IntelliJ (but not Ant) compilation fails on branch_4x and trunk using Java6; Java7 works for all

DK 1.6.0_32. - Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Wednesday, August 22, 2012 4:25 PM To: dev@lucene.apache.org Subject: Maven and IntelliJ (but not Ant) compilation fails on branch_4x and trunk using Java6; Java7 works for all On Win7, I'm getting compilat

Maven and IntelliJ (but not Ant) compilation fails on branch_4x and trunk using Java6; Java7 works for all

On Win7, I'm getting compilation failures on branch_4x and trunk, under Maven (2.2.1 and 3.0.4) and IntelliJ (11.1.3). Under Ant (1.8.2), compilation succeeds. I've tried Oracle JDK 1.6.0_21 and 1.6.0_34, both 64-bit, and both behave the same (success under Ant, failure under Maven and Intelli

RE: Looking for a code pattern to pass stop words as an attribute

Hi Dawid, Maybe you could use KeywordMarkerFilter, either directly or as a recipe for a StopwordMarkerFilter? Note that KeywordAttribute is used by most (all?) Lucene stemmers, so I wouldn't use KeywordMarkerFilter if your analysis chain already includes a stemmer. Steve -Original Mess

RE: Making a contribution to Lucene - please help

Hi Catherine, Welcome! I assume you are the same person as "jellyman" who posted earlier in this mailing list about exactly this same topic? If so, FYI, someone posting under multiple identities can be a predictor for various forms of mailing list nastiness, so you might want to pick one iden

RE: large messages from Jenkins failures

+1 to using -Dtests.showOutput=never for Jenkins jobs. - Steve -Original Message- From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid Weiss Sent: Monday, August 20, 2012 2:20 PM To: dev@lucene.apache.org Subject: Re: large messages from Jenkins failures This is

RE: Compilation issues

Hi Itamar, I use Oracle JDK v1.7.0_01 64-bit with IntelliJ v11.1.3 on Windows 7, and it works fine for me - I just did a full rebuild (Build|Rebuild Project) from a fresh trunk checkout, and compilation of all of Lucene/Solr succeeded with no errors. Have you seen

RE: Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

Another possibility that would increase customizability via exposing information we currently throw away, proposed by Mike McCandless on LUCENE-3940[1] (though controversially[2]): in addition to tokenizing alpha/numeric char sequences, StandardTokenizer could also tokenize everything else. Th

JIRA is back up

https://twitter.com/infrabot/statuses/234713391812448256 - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #570: POMs out of sync

Mark Miller introduced new dependencies from the solr test-framework on jetty-servlet, jetty-util, and servlet-api - this caused compilation failures under Maven, since these jars were not included in the compilation classpath: -- [INFO] Compilation failure /usr/home/hudson/hudson-slave/wor

RE: svn commit: r1369987 - in /lucene/dev/nightly: common-maven.sh hudson-settings.sh

> -RHINO_LIBS_DIR=/usr/home/hudson/tools/java/openjdk-missing-libs > +RHINO_LIBS_DIR=$HOME/tools/java/openjdk-missing-libs Thanks Uwe. - Steve

RE: Suggestion: Link to web access for Lucene source

Hi Jack, You can anonymously make edits to this page (or any other page on any Apache CMS site), and your patch will be sent to the dev list for commit handling. See - there's a link there for a video tutorial. Steve From: Jack Krupansky

RE: svn commit: r1366336 - in /lucene/dev/branches/branch_4x: ./ lucene/ lucene/analysis/ lucene/analysis/common/src/java/org/apache/lucene/analysis/standard/ lucene/analysis/common/src/java/org/apach

Thanks Uwe. - Steve -Original Message- From: uschind...@apache.org [mailto:uschind...@apache.org] Sent: Friday, July 27, 2012 7:03 AM To: comm...@lucene.apache.org Subject: svn commit: r1366336 - in /lucene/dev/branches/branch_4x: ./ lucene/ lucene/analysis/ lucene/analysis/common/src/j

RE: [JENKINS] Lucene-4.x - Build # 49 - Failure

Committed javadoc fix in r1366300. - Steve -Original Message- [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.6.0_32 [javadoc] Building tree for all the packages and classes... [javadoc] /usr/home/hudson/hudson-slave/workspace/Lucene-4.x/checkout/

RE: [DISCUSS] define what/when a 4.0-beta should be

I vote for proceeding with the existing plan: alpha, beta at least one month later, final at least one month later: roughly your #2, Robert. Sticking to the plan seems worth the (potential) extra month wait to me. - Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] S

RE: top level "ant test" shouldn't validate?

On 7/19/2012 at 12:35 PM, Michael McCandless wrote: > Any objections to fixing top level "ant test" to simply run tests...? > > Maybe we can add a "precommit" target to run tests, validate, javadocs-lint, > ... +1 Steve - To un

RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 487 - Failure!

Linux-Java6-64/checkout/lucene/benchmark/lib/nekohtml-1.9.15.jar -Original Message- From: Policeman Jenkins Server [mailto:jenk...@sd-datasolutions.de] Sent: Sunday, July 15, 2012 1:49 PM To: dev@lucene.apache.org; rm...@apache.org; Steven A Rowe; markrmil...@apache.org; u...@thetaphi.de Su

RE: Jenkins email notification regexes [was: RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!]

I've adjusted the regexes on Uwe's Jenkins and on the Lucene & Solr jobs on ASF Jenkins. - Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Monday, July 09, 2012 12:09 PM To: dev@lucene.apache.org Subject: RE: Jenkins email notification re

[DISCUSS] Adding ASF comment system to the Lucene websites

I'd like to add the new ASF comment system to the Lucene websites: https://blogs.apache.org/infra/entry/asf_comments_system_live Thoughts? Steve - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional comma

Solrj lucene-core dependency [was: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #540: POMs out of sync]

As part of LUCENE-4199, a lucene-core dependency was added to Solrj, in ContentStreamBase.java: 133: public Reader getReader() throws IOException { 134: String charset = getCharsetFromContentType( contentType ); 135: return charset == null 136: ? new InputStreamReader(getStream(), IOUtil

RE: Problems setting up Lucene project in Eclipse

Hi Svetlana, "ant eclipse" only works from the top-level directory *containing* Lucene - in addition to the lucene/ directory, your Subversion checkout needs to have the dev-tools/ directory - that's where the eclipse configuration is. (When you check out this top-level directory, you'll also

RE: Jenkins email notification regexes [was: RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!]

ailed, see log. On Sun, Jul 8, 2012 at 2:04 AM, Steven A Rowe wrote: > I've updated the regexes on Uwe's Jenkins and on the Lucene & Solr jobs on > ASF Jenkins to capture all of the interesting stuff I know about. (E.g., > [junit4] recently became [junit4:junit4].)

RE: Jenkins email notification regexes [was: RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!]

I wasn't trying to complain, just noting the change as an example of trivial differences that can break regexes. This stuff is going to change over time, it's to be expected. Hopefully email notifications will spend less time out of sync with logging than in. Steve -Original Message-

Jenkins email notification regexes [was: RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!]

x27;ll try to adjust the regexes. Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Monday, July 02, 2012 6:03 PM To: dev@lucene.apache.org Subject: RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing! On Uwe's Jenkins, the regul

RE: [JENKINS] Lucene-Solr-4.x-Windows-Java6-64 - Build # 260 - Failure!

did not install any SVN at all. -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de Steven A Rowe mailto:sar...@syr.edu>> schrieb: There is a subversion problem here unrelated to the test failure - from the log: jar-core: [exec] Execute failed: java.io<http:

RE: [JENKINS] Lucene-Solr-4.x-Windows-Java6-64 - Build # 260 - Failure!

There is a subversion problem here unrelated to the test failure - from the log: jar-core: [exec] Execute failed: java.io.IOException: Cannot run program "svnversion" (in directory "C:\Jenkins\workspace\Lucene-Solr-4.x-Windows-Java6-64\lucene\queries"): CreateProcess error=2, The system ca

RE: Solr 3.6.0 javadocs are missing from the site

I restored the Solr 3.6.0 javadocs at : - Added line "solr/api-3_6_0" to extpaths.txt on the CMS source tree. - Restored and renamed the javadocs directory: svn -m "bring Solr 3.6.0 javadocs back to life" copy \ https://svn.apache.org/repos/infra/websit

Opportunity at O'Reilly Open Source Convention (OSCON)

Apache will be hosting a series of events in the two days prior to OSCON, the 16th and 17th of July. These events are a unique opportunity to engage new participants and build awareness for Lucene and Solr. The goal is to provide an environment where newcomers and veteran Apache contributors alik

RE: buildbot failure in ASF Buildbot on lucene-site-staging

Here's the changed section of the ReleaseTodo wiki page: <http://wiki.apache.org/lucene-java/ReleaseTodo#Pushing_website_changes_.26_Announcing>. -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Tuesday, July 03, 2012 3:49 AM To: dev@lucene.apache.org; s

RE: buildbot failure in ASF Buildbot on lucene-site-staging

FYI, I've managed to commit the 4.0.0-ALPHA javadocs, with help from Joe Schaefer and Gavin McDonald on #asfinfra. I'm writing it up on the ReleaseTodo wiki page now. Steve -Original Message- From: Simon Willnauer [mailto:simon.willna...@gmail.com] Sent: Tuesday, July 03, 2012 3:44 AM

RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!

On Uwe's Jenkins, the regular expression used to extract failures for email notification isn't pulling everything out that it should, e.g. this email is missing javadocs-lint output. I'm collecting examples of problems (failures to extract failures) and will work on fixing some time this week.

RE: question about maven artifacts publishing instructions

artifacts' and that the appropriate files were signed, ordinarily using 'ant sign-artifacts'. Steve -Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Friday, June 29, 2012 1:17 PM To: dev@lucene.apache.org Subject: RE: question about maven artifacts pub

RE: question about maven artifacts publishing instructions

bout maven artifacts publishing instructions On Fri, Jun 29, 2012 at 12:57 PM, Steven A Rowe wrote: > Was it a parent directory of both the Lucene and the Solr artifacts? > yes. is this a problem? -- lucidimagination.com

RE: question about maven artifacts publishing instructions

Hmm, interesting. When I wrote those instructions in the process of performing them for the last release, the Lucene invocation only staged the Lucene artifacts, likewise for the Solr invocation and artifacts. Where did the artifacts come from? Did you use the download script referred to in t

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

Hmm, this is likely a Maven Surefire-only problem. I'm clueless about the interaction between Surefire your randomized runner, Dawid - should this test be ignored under Surefire? Under other test runners too, maybe? (IntelliJ, Eclipse) Steve -Original Message- From: Steven A

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

Dawid, You checked in changes to this test (TestMaxFailuresRule.java) at revision 1355279. This Jenkins Maven build's checked out svn revision is 1355359. So it looks like there might be a problem with your commit? Steve -Original Message- From: Apache Jenkins Server [mailto:jenk...@

regular but not individually reproducible failure: TestIndexWriterWithThreads.testRollbackAndCommitWithThreads

I see this roughly 50% of the time I run all Lucene core tests (Win7 64, Sun JDK 1.6.0_21 64-bit), but the seeds don't reproduce the error when it's run individually. The only unusual thing I'm doing on this machine is running some web crawls in a VirtualBox Linux VM, hosted on and writing to a

RE: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 1078 - Failure!

This failure is due to a javadocs warning: [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.6.0_32 [javadoc] Building tree for all the packages and classes... [javadoc] /mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux-Java6-64/checkout/lucene/spatial/src

RE: Welcome Greg Bowyer

Welcome, Greg! -Original Message- From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid Weiss Sent: Thursday, June 21, 2012 7:00 AM To: dev@lucene.apache.org Subject: Re: Welcome Greg Bowyer Congratulations, Greg! (but I still think AspectJ log parsing is more ve

RE: Regex causes stack overflow!

y, I'll un-revert and include these changes on the email notification configuration for our jobs on the Apache Jenkins instance. Steve -----Original Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Sunday, June 17, 2012 3:16 PM To: dev@lucene.apache.org Subject: RE: Regex causes s

RE: Failed to execute goal org.apache.felix:maven-bundle-plugin:2.3.4:manifest (bundle-manifest) on project lucene-test-framework

Hi Fuad, I didn't get this error on trunk when I ran "mvn -DskipTests install" from the top-level directory just now. What command did you give? What version/vendor of Java and version of Maven are you using? What operating system? Steve From: Fuad Efendi [mailto:fuad.efe...@tokenizer.ca] S

RE: Regex causes stack overflow!

I couldn't tell from the look of it. We could really make use of those non-backtracking regexps :) Dawid On Sun, Jun 17, 2012 at 8:36 PM, Steven A Rowe wrote: > On 6/17/2012 at 11:42 AM, Uwe Schindler wrote: >> We had a failed build last night, but no eMail was sent! So I looked

RE: Regex causes stack overflow!

On 6/17/2012 at 11:42 AM, Uwe Schindler wrote: > We had a failed build last night, but no eMail was sent! So I looked into > the server's log, and found the following - something in your regex seems > to cause a stack overflow (this is not shown in the build log itself, only > the server log). The

RE: [JENKINS] Lucene-Solr-trunk-Windows-Java6-64 - Build # 518 - Failure!

I added to the email notification regex in all non-Maven ASF Jenkins jobs to capture this failure: > ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due > to exception hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: > java.net.SocketException: >

RE: VOTE: Lucene/Solr 4.0-ALPHA

I ran smokeTestRelease.py on Windows+Cygwin. Several "***WARNING***: javadocs want to fail!" messages. And also javadocs warnings that did trigger a failure under Solr: unpack apache-solr-4.0.0-ALPHA.zip... test solr example w/ Java 6... File "/home/s/svn/lucene/dev/branches/branch_4

RE: VOTE: Lucene/Solr 4.0-ALPHA

Changes.html had a couple of problems related to the JIRA REST API URL changing (missing release dates, compound release numbers missing the second release number). I've modified changes2html.pl to use the new URL. Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] S

RE: svn commit: r1348294 - in /lucene/dev/trunk: ./ lucene/ lucene/site/ lucene/site/changes/changes2html.pl

Thanks for the heads-up, Robert - I simplified the regex a little and it still seems to work. - Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Saturday, June 09, 2012 7:08 AM To: dev@lucene.apache.org Subject: Re: svn commit: r1348294 - in /lucene/dev/trunk: .

RE: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 838 - Failure!

ag On Jun 9, 2012 8:58 PM, "Robert Muir" mailto:rcm...@gmail.com>> wrote: I think there is a hardcoded whitelist in the script of apache.org<http://apache.org> domains to check for sketchy links On Jun 9, 2012 8:52 PM, "Steven A Rowe" mailto:sar...@syr.edu>> wr

RE: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 838 - Failure!

I committed a change to changes2html.pl that linkifies URLs in CHANGES.txt. javadocs-lint is complaining about two of these, but the links work for me, so I'm not sure what's happening. I'll look at the python link checking script. Steve -Original Message- From: jenk...@sd-datasolution

RE: Spurious JFlex warning from build

+1 From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Friday, June 08, 2012 1:48 PM To: Lucene/Solr Dev Subject: Spurious JFlex warning from build I happened to notice the following message in an ant test today: compile-test: [echo] Building analyzers-common... jflex-uptodate-check

RE: Welcome Adrien Grand as a new Lucene/Solr committer

Congratulations and welcome, Adrian! - Steve -Original Message- From: Michael McCandless [mailto:luc...@mikemccandless.com] Sent: Thursday, June 07, 2012 2:12 PM To: Lucene/Solr dev Subject: Welcome Adrien Grand as a new Lucene/Solr committer I'm pleased to announce that Adrien Grand has

RE: [JENKINS] Lucene-Solr-4.x-Windows-Java7-64 - Build # 9 - Failure!

My guess: Ant uses the junit4 jar, and clean now tries to delete it (LUCENE-4115). M$ no likey. From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Thursday, June 07, 2012 9:37 AM To: dev@lucene.apache.org; markrmil...@gmail.com Subject: RE: [JENKINS] Lucene-Solr-4.x-Windows-Java7-64 - Build # 9

RE: remove "via"

+1 Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Tuesday, June 05, 2012 6:40 PM To: dev@lucene.apache.org Subject: remove "via" Hello, Currently we do this in CHANGES.txt: LUCENE-: Fixed a horrible nasty bug. (Joe Contributor via John Doe Committer)

RE: [JENKINS] Lucene-Solr-tests-only-trunk - Build # 14586 - Still Failing

I added another regex to the non-Maven Jenkins jobs' "Editable Email Notification"/"Default Content" configuration to capture missing sha1 files from 'ant validate': ${BUILD_LOG_REGEX,regex="[ \\t]\\[licenses\\] MISSING sha1",linesBefore=2,linesAfter=1} Steve -Original Message- From:

RE: [JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 701 - Failure!

This job's console output includes a thread dump - to capture it for inclusion in the email notification, I've added the following to the ASF non-Maven Jenkins jobs' "Editable Email Notification"/"Default Content": ${BUILD_LOG_REGEX,regex="[ \\t]Full thread dump",linesBefore=1,linesAfte

Re: [JENKINS] Lucene-Solr-tests-only-trunk - Build # 14493 - Failure

Yeah there are four regexes now - only one seems problematic. On mobile now - I'll fix when I get to a workstation later today. Uwe Schindler wrote: Some problem with the regex! Uwe -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de Apache Jenkins Server schrieb:

RE: [JENKINS] Lucene-Solr-tests-only-trunk-java7 - Build # 2723 - Failure

Hmm, looks like spreading the BUILD_LOG_REGEX across multiple lines caused it not to be recognized. Jenkins's email templating functionality is provided by the Jenkins Email Extension Plugin (email-ext) . The token parsing is done b

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync

I just committed a fix: it was a version property in build.xml -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Wednesday, May 30, 2012 10:48 AM To: dev@lucene.apache.org Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync I figured this would

RE: [JENKINS] Lucene-trunk - Build # 1942 - Failure

Interesting. How did you run it to reproduce? Did you use the linesfile? Because without it I'm not able to reproduce this. Downloading the lines file now. Dawid On Sat, May 26, 2012 at 5:07 PM, Steven A Rowe wrote: > Reproduces 100% for me. > > -Original Message- > Fro

  1   2   3   4   5   >