Re: Welcome Alan Woodward as Lucene/Solr committer

2012-10-17 Thread Steven A Rowe
Welcome Alan! Alan Woodward alan.woodw...@romseysoftware.co.uk 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

RE: VOTE: release 4.0 (RC2)

2012-10-07 Thread Steven A Rowe
+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

RE: [DISCUSS] TM in website graphic images

2012-09-28 Thread Steven A Rowe
@lucene.apache.org Subject: Re: [DISCUSS] TM in website graphic images On Thu, Sep 27, 2012 at 7:59 PM, Steven A Rowe sar...@syr.edu wrote: ... ensure that it includes a small TM symbol in the graphic or immediately adjacent to it. For pages that include the poject logo

RE: [DISCUSS] TM in website graphic images

2012-09-28 Thread Steven A Rowe
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 - this is a list of products, not top-level projects

RE: VOTE: release 4.0 (take two)

2012-09-27 Thread Steven A Rowe
+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

[DISCUSS] TM in website graphic images

2012-09-27 Thread Steven A Rowe
I want to finish addressing the Project Branding Requirements at http://www.apache.org/foundation/marks/pmcs.html. One of the outstanding issues is stamping our graphics with TM. From http://www.apache.org/foundation/marks/pmcs.html#graphics: Logos are important to recognize as

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

2012-09-26 Thread Steven A Rowe
+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

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

2012-09-26 Thread Steven A Rowe
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:

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

2012-09-26 Thread Steven A Rowe
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 Subject: RE: svn commit: r1390535 - in /lucene/dev/branches/branch_4x: ./ dev-tools

RE: VOTE: release 4.0

2012-09-25 Thread Steven A Rowe
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 sar...@syr.edu 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 reflection on this release

RE: Smoke test instructions

2012-09-25 Thread Steven A Rowe
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: Re:VOTE: release 4.0

2012-09-24 Thread Steven A Rowe
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,

RE: VOTE: release 4.0

2012-09-24 Thread Steven A Rowe
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

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

2012-09-22 Thread Steven A Rowe
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

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

2012-09-22 Thread Steven A Rowe
nightly-smoke -DJAVA6_HOME= -DJAVA7_HOME=' On Sat, Sep 22, 2012 at 11:29 AM, Steven A Rowe sar...@syr.edu 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? Against a file:// url built

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

2012-09-22 Thread Steven A Rowe
the lucene_solr_4_0 release branch and runs 'ant nightly-smoke -DJAVA6_HOME= -DJAVA7_HOME=' On Sat, Sep 22, 2012 at 11:29 AM, Steven A Rowe sar...@syr.edu wrote: The maven checks use python XML parsing, which appears to be complaining about well-formedness of a POM file. How is smoketester being

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

2012-09-22 Thread Steven A Rowe
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

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

2012-09-17 Thread Steven A Rowe
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....

2012-09-16 Thread Steven A Rowe
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

RE: SonaType repo in Maven POMs

2012-09-07 Thread Steven A Rowe
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

RE: SonaType repo in Maven POMs

2012-09-07 Thread Steven A Rowe
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

2012-09-07 Thread Steven A Rowe
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: SonaType repo in Maven POMs

2012-09-07 Thread Steven A Rowe
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 build from both

RE: SonaType repo in Maven POMs

2012-09-07 Thread Steven A Rowe
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*

RE: SonaType repo in Maven POMs

2012-09-07 Thread Steven A Rowe
, 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

2012-09-07 Thread Steven A Rowe
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, September 07, 2012 8:21

RE: JIRA assign issue

2012-09-06 Thread Steven A Rowe
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

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

2012-09-06 Thread Steven A Rowe
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

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

2012-09-05 Thread Steven A Rowe
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

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

2012-09-05 Thread Steven A Rowe
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

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

2012-09-05 Thread Steven A Rowe
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 sar

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

2012-08-30 Thread Steven A Rowe
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: large messages from Jenkins failures

2012-08-30 Thread Steven A Rowe
, 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 Message- From: Steven A Rowe [mailto:sar...@syr.edu] Sent: Tuesday

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

2012-08-30 Thread Steven A Rowe
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: [JENKINS] Lucene-Solr-4.x-Linux (64bit/ibm-j9-jdk7) - Build # 752 - Failure!

2012-08-30 Thread Steven A Rowe
this later today. Thanks Steve. Sent from mobile phone. On Aug 30, 2012 5:18 PM, Steven A Rowe sar...@syr.edu wrote: 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

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

2012-08-29 Thread Steven A Rowe
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 PM

RE: large messages from Jenkins failures

2012-08-28 Thread Steven A Rowe
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=never for Jenkins

RE: large messages from Jenkins failures

2012-08-28 Thread Steven A Rowe
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 a

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

2012-08-28 Thread Steven A Rowe
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

RE: Problems with ivy resolution

2012-08-26 Thread Steven A Rowe
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

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

2012-08-25 Thread Steven A Rowe
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;

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

2012-08-14 Thread Steven A Rowe
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.

JIRA is back up

2012-08-12 Thread Steven A Rowe
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

2012-08-08 Thread Steven A Rowe
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

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

2012-08-06 Thread Steven A Rowe
-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

2012-08-03 Thread Steven A Rowe
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 http://www.apache.org/dev/cmsref.html#non-committer - there's a link there for a video tutorial. Steve From: Jack Krupansky

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

2012-07-27 Thread Steven A Rowe
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]

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

2012-07-27 Thread Steven A Rowe
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/

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

2012-07-24 Thread Steven A Rowe
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]

RE: top level ant test shouldn't validate?

2012-07-19 Thread Steven A Rowe
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

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

2012-07-15 Thread Steven A Rowe
-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 Subject

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

2012-07-09 Thread Steven A Rowe
, see log. On Sun, Jul 8, 2012 at 2:04 AM, Steven A Rowe sar...@syr.edu 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].) If you notice

RE: Problems setting up Lucene project in Eclipse

2012-07-09 Thread Steven A Rowe
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

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

2012-07-09 Thread Steven A Rowe
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(),

[DISCUSS] Adding ASF comment system to the Lucene websites

2012-07-09 Thread Steven A Rowe
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

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

2012-07-09 Thread Steven A Rowe
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 regexes [was: RE

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

2012-07-08 Thread Steven A Rowe
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 regular expression used to extract

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

2012-07-08 Thread Steven A Rowe
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-

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

2012-07-07 Thread Steven A Rowe
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

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

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

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

2012-07-03 Thread Steven A Rowe
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

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

2012-07-03 Thread Steven A Rowe
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; simon.willna

Opportunity at O'Reilly Open Source Convention (OSCON)

2012-07-03 Thread Steven A Rowe
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

RE: Solr 3.6.0 javadocs are missing from the site

2012-07-03 Thread Steven A Rowe
I restored the Solr 3.6.0 javadocs at http://lucene.apache.org/solr/api-3_6_0/: - 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 \

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

2012-07-02 Thread Steven A Rowe
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: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #14: POMs out of sync

2012-06-29 Thread Steven A Rowe
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

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

2012-06-29 Thread Steven A Rowe
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 Rowe

RE: question about maven artifacts publishing instructions

2012-06-29 Thread Steven A Rowe
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

RE: question about maven artifacts publishing instructions

2012-06-29 Thread Steven A Rowe
artifacts publishing instructions On Fri, Jun 29, 2012 at 12:57 PM, Steven A Rowe sar...@syr.edu 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

2012-06-29 Thread Steven A Rowe
' 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 publishing instructions I think it's fine

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

2012-06-28 Thread Steven A Rowe
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]

regular but not individually reproducible failure: TestIndexWriterWithThreads.testRollbackAndCommitWithThreads

2012-06-28 Thread Steven A Rowe
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

RE: Welcome Greg Bowyer

2012-06-21 Thread Steven A Rowe
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

RE: Regex causes stack overflow!

2012-06-17 Thread Steven A Rowe
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: Regex causes stack overflow!

2012-06-17 Thread Steven A Rowe
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 sar...@syr.edu 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 into the server's log

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

2012-06-17 Thread Steven A Rowe
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]

RE: Regex causes stack overflow!

2012-06-17 Thread Steven A Rowe
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 stack overflow! Good ideas, thanks Dawid

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

2012-06-13 Thread Steven A Rowe
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

2012-06-10 Thread Steven A Rowe
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

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

2012-06-09 Thread Steven A Rowe
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:

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

2012-06-09 Thread Steven A Rowe
8:58 PM, Robert Muir rcm...@gmail.commailto:rcm...@gmail.com wrote: I think there is a hardcoded whitelist in the script of apache.orghttp://apache.org domains to check for sketchy links On Jun 9, 2012 8:52 PM, Steven A Rowe sar...@syr.edumailto:sar...@syr.edu wrote: I committed a change

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

2012-06-09 Thread Steven A Rowe
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: VOTE: Lucene/Solr 4.0-ALPHA

2012-06-09 Thread Steven A Rowe
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]

RE: Spurious JFlex warning from build

2012-06-08 Thread Steven A Rowe
+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...

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

2012-06-07 Thread Steven A Rowe
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 #

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

2012-06-05 Thread Steven A Rowe
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: remove via

2012-06-05 Thread Steven A Rowe
+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-trunk-Linux-Java6-64 - Build # 701 - Failure!

2012-06-04 Thread Steven A Rowe
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

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

2012-06-01 Thread Steven A Rowe
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 u...@thetaphi.de wrote: Some problem with the regex! Uwe -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de Apache Jenkins

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

2012-05-31 Thread Steven A Rowe
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) https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin. The token parsing is done by

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

2012-05-30 Thread Steven A Rowe
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

2012-05-26 Thread Steven A Rowe
Reproduces 100% for me. -Original Message- From: Apache Jenkins Server [mailto:jenk...@builds.apache.org] Sent: Friday, May 25, 2012 11:11 PM To: dev@lucene.apache.org Subject: [JENKINS] Lucene-trunk - Build # 1942 - Failure Build: https://builds.apache.org/job/Lucene-trunk/1942/ 1

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

2012-05-26 Thread Steven A Rowe
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 sar...@syr.edu wrote: Reproduces 100% for me. -Original Message- From: Apache

RE: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

2012-05-18 Thread Steven A Rowe
I think this can happen when your Ivy cache gets corrupted, and can be fixed by clearing the Ivy cache, triggering a re-download. (To automate this, we could wrap the ivy:cleancache/ ant task: http://ant.apache.org/ivy/history/2.2.0/use/cleancache.html.) Steve From: Smiley, David W.

RE: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

2012-05-18 Thread Steven A Rowe
I don't think so, because the expected checksum is the correct checksum (at least, that's what I get when I manually checksum the jar in question): 384faa82e193d4e4b0546059ca09572654bc3970 *commons-fileupload-1.2.1.jar Steve From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Friday,

RE: Clean-jars.

2012-05-15 Thread Steven A Rowe
Hi Dawid, After updating, I ran through all of the module test run configurations on IntelliJ, and one test failed: java.lang.RuntimeException: There are overridden methods annotated with org.junit.Before. These methods would not be executed by JUnit and need to manually chain

RE: Clean-jars.

2012-05-15 Thread Steven A Rowe
Thanks, Dawid The result is strange - a red (X) still appears next to this test, but the overall result bar stays green, and the same exception gets printed out. Here's a screen grab showing this: http://i46.tinypic.com/syknja.png (unless you know of a way to restrict it to Test* classes)

[MAVEN] Heads up: build changes

2012-05-08 Thread Steven A Rowe
If you use the Lucene/Solr Maven POMs to drive the build, I committed a major change last night (see https://issues.apache.org/jira/browse/LUCENE-3948 for more details): * 'ant get-maven-poms' no longer places pom.xml files under the lucene/ and solr/ directories. Instead, they are placed in

RE: svn commit: r1332886 - /lucene/dev/trunk/lucene/analysis/common/src/test/org/apache/lucene/analysis/core/TestUAX29URLEmailTokenizer.java

2012-05-01 Thread Steven A Rowe
Thanks, Robert. - Steve -Original Message- From: rm...@apache.org [mailto:rm...@apache.org] Sent: Tuesday, May 01, 2012 8:11 PM To: comm...@lucene.apache.org Subject: svn commit: r1332886 -

RE: Maven

2012-04-27 Thread Steven A Rowe
On 4/27/2012 at 9:10 AM, Benson Margulies wrote: 1: Should the Lucene PMC publish maven artifacts at all? - There seems to remain a consensus of the community: Yes. Not really: consensus means unanimous agreement. The rest of your points, Benson, confuse Maven issues around 3rd party

  1   2   3   4   5   6   >