[jira] [Resolved] (PYLUCENE-52) JCC build fails with Python 3.8.

[ https://issues.apache.org/jira/browse/PYLUCENE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Coady resolved PYLUCENE-52. -- Resolution: Fixed > JCC build fails with Python

[jira] [Updated] (PYLUCENE-52) JCC build fails with Python 3.8.

[ https://issues.apache.org/jira/browse/PYLUCENE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Allouche updated PYLUCENE-52: --- Attachment: pylucene-lpython.patch > JCC build fails with Python

[jira] [Commented] (PYLUCENE-52) JCC build fails with Python 3.8.

3.8. [^pylucene-lpython.patch] > JCC build fails with Python 3.8. > > > Key: PYLUCENE-52 > URL: https://issues.apache.org/jira/browse/PYLUCENE-52 > Project: PyLucene > Issue Type: Bug >

Re: [jira] [Created] (PYLUCENE-52) JCC build fails with Python 3.8.

That, and, with python 3.8, extensions are not supposed to be explicitely linked against libpython anymore. (from the same doc) > On Oct 15, 2019, at 18:53, A. Coady (Jira) wrote: > > A. Coady created PYLUCENE-52: > > > Summar

[jira] [Created] (PYLUCENE-52) JCC build fails with Python 3.8.

A. Coady created PYLUCENE-52: Summary: JCC build fails with Python 3.8. Key: PYLUCENE-52 URL: https://issues.apache.org/jira/browse/PYLUCENE-52 Project: PyLucene Issue Type: Bug

[jira] [Commented] (SOLR-13549) Maven build fails to build Solr core tests due to missing dependency

[ https://issues.apache.org/jira/browse/SOLR-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867391#comment-16867391 ] Cao Manh Dat commented on SOLR-13549: - Thanks [~dancollins] > Maven build fails to build Solr c

[jira] [Resolved] (SOLR-13549) Maven build fails to build Solr core tests due to missing dependency

was merged as part of SOLR-13434, so this is fixed. > Maven build fails to build Solr core tests due to missing dependency > > > Key: SOLR-13549 > URL: https://issues.apache.org/jira/br

[jira] [Commented] (SOLR-13549) Maven build fails to build Solr core tests due to missing dependency

?focusedCommentId=16861794=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16861794 > Maven build fails to build Solr core tests due to missing dependency > > > Key

[jira] [Updated] (SOLR-13549) Maven build fails to build Solr core tests due to missing dependency

ven build fails to build Solr core tests due to missing dependency > > > Key: SOLR-13549 > URL: https://issues.apache.org/jira/browse/SOLR-13549 > Project: Solr >

[jira] [Created] (SOLR-13549) Maven build fails to build Solr core tests due to missing dependency

Daniel Collins created SOLR-13549: - Summary: Maven build fails to build Solr core tests due to missing dependency Key: SOLR-13549 URL: https://issues.apache.org/jira/browse/SOLR-13549 Project: Solr

[jira] [Commented] (PYLUCENE-42) JCC build fails with Python 3.7 (release candidate).

[ https://issues.apache.org/jira/browse/PYLUCENE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505050#comment-16505050 ] Andi Vajda commented on PYLUCENE-42: Patch applied, thank you for the fix ! > JCC build fa

[jira] [Resolved] (PYLUCENE-42) JCC build fails with Python 3.7 (release candidate).

[ https://issues.apache.org/jira/browse/PYLUCENE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Vajda resolved PYLUCENE-42. Resolution: Fixed > JCC build fails with Python 3.7 (release candid

[jira] [Commented] (PYLUCENE-42) JCC build fails with Python 3.7 (release candidate).

[ https://issues.apache.org/jira/browse/PYLUCENE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504169#comment-16504169 ] A. Coady commented on PYLUCENE-42: -- Adding {{const}} fixes issue. > JCC build fails with Python

[jira] [Updated] (PYLUCENE-42) JCC build fails with Python 3.7 (release candidate).

[ https://issues.apache.org/jira/browse/PYLUCENE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Coady updated PYLUCENE-42: - Attachment: patch.txt > JCC build fails with Python 3.7 (release candid

Re: [jira] [Created] (PYLUCENE-42) JCC build fails with Python 3.7 (release candidate).

Could you please add the missing 'const' and see if that's the only such compile error ? Thanks ! Andi.. > On Jun 6, 2018, at 17:06, A. Coady (JIRA) wrote: > > A. Coady created PYLUCENE-42: > > > Summary: JCC build fails with P

[jira] [Created] (PYLUCENE-42) JCC build fails with Python 3.7 (release candidate).

A. Coady created PYLUCENE-42: Summary: JCC build fails with Python 3.7 (release candidate). Key: PYLUCENE-42 URL: https://issues.apache.org/jira/browse/PYLUCENE-42 Project: PyLucene Issue Type

[jira] [Commented] (LUCENE-8189) Build fails with ant version 1.10.x

. > Build fails with ant version 1.10.x > --- > > Key: LUCENE-8189 > URL: https://issues.apache.org/jira/browse/LUCENE-8189 > Project: Lucene - Core > Issue Type: Bug > Components: ge

[jira] [Commented] (LUCENE-8189) Build fails with ant version 1.10.x

. We can fail the same way. > Build fails with ant version 1.10.x > --- > > Key: LUCENE-8189 > URL: https://issues.apache.org/jira/browse/LUCENE-8189 > Project: Lucene - Core > Issue Type: Bug

[jira] [Commented] (LUCENE-8189) Build fails with ant version 1.10.x

it check the versions of all relevant tools and fail with a helpful message if they are outside of the range that we consider acceptable. > Build fails with ant version 1.10.x > --- > > Key: LUCENE-8189 >

[jira] [Commented] (LUCENE-8189) Build fails with ant version 1.10.x

around it. We might only add a check for the exact ANT version to our common-build.xml that fails early with a message "don't user ANT 1.10.2" > Build fails with ant version 1.10.x > --- > > Key: LUCENE-8189 >

[jira] [Commented] (LUCENE-8189) Build fails with ant version 1.10.x

, [~erickoerickson] mentioned that 1.10.1 works. So this might indeed be a bug in ant. I only tried 1.10.2. I hadn't gotten around to replying to the mailing list thread yet. > Build fails with ant version 1.10.x > --- > > Key:

[jira] [Resolved] (LUCENE-8189) Build fails with ant version 1.10.x

/wshnt7ok2rlvy5w7. > Build fails with ant version 1.10.x > --- > > Key: LUCENE-8189 > URL: https://issues.apache.org/jira/browse/LUCENE-8189 > Project: Lucene - Core > Issue Type: Bug > C

[jira] [Commented] (LUCENE-8189) Build fails with ant version 1.10.x

.  If this is a duplicate, feel free to close as a duplicate. Although it's always possible that this is a bug in Ant, that seems unlikely. Version 1.10 has been out for more than a year, and is on its third point release. > Build fails with ant version 1.1

[jira] [Created] (LUCENE-8189) Build fails with ant version 1.10.x

Shawn Heisey created LUCENE-8189: Summary: Build fails with ant version 1.10.x Key: LUCENE-8189 URL: https://issues.apache.org/jira/browse/LUCENE-8189 Project: Lucene - Core Issue Type: Bug

[jira] [Updated] (LUCENE-6673) Maven build fails for target javadoc:jar

[ https://issues.apache.org/jira/browse/LUCENE-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-6673: --- Summary: Maven build fails for target javadoc:jar (was: Maven build fails for target javadoc:jar

[jira] [Resolved] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

and Ramkumar. > Maven build fails for target javadoc:jar on trunk/Java8 > --- > > Key: LUCENE-6673 > URL: https://issues.apache.org/jira/browse/LUCENE-6673 > Project: Lucene - Core >

[jira] [Commented] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

0062e999203fb6dbb7bd9d37e1c4a95cc2367504 in lucene-solr's branch refs/heads/master from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0062e99 ] LUCENE-6673: Maven build fails for target javadoc:jar. > Maven build fails for target javadoc:jar on trunk/Ja

[jira] [Assigned] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

[ https://issues.apache.org/jira/browse/LUCENE-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe reassigned LUCENE-6673: -- Assignee: Steve Rowe (was: Ramkumar Aiyengar) > Maven build fails for target javadoc:

[jira] [Commented] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

9c10d2ab176ef41f7380382ab16c81af3c7933d7 in lucene-solr's branch refs/heads/branch_7x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9c10d2a ] LUCENE-6673: Maven build fails for target javadoc:jar. > Maven build fails for target javadoc:jar on trunk/Ja

[jira] [Commented] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

the settings that common-build.xml uses (for ant). We are trying to move to branch_7x and test on master, and without this we can't build javadocs (fails at the first hurdle of Lucene core) > Maven build fails for target javadoc:jar on trunk/Ja

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

, but as the Javadocs fix was declared a security issue, I assume that it is also applied to Java 7, so without this fix Java 7 paid updates will fail the build, too. > Javadocs build fails with Java 8 update 121 > --- > > Key:

RE: [jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

> Sent: Tuesday, February 7, 2017 11:44 AM > To: dev@lucene.apache.org > Subject: [jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 > update 121 > > > [ https://issues.apache.org/jira/browse/LUCENE- > 7651?page=com.atlassian.jira.plugin.system.issuetabpanel

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

ent to the Changelog that prettyprinting Javadocs is no longer working, if docs are build with Java 7. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/brows

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

's -bottom parameter. Also update Prettify to latest version to fix Google Chrome issue. # Conflicts: # lucene/CHANGES.txt > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

9dcfcb6e6fcbab36d50c4baca697c1104c2a72ff in lucene-solr's branch refs/heads/master from [~jpountz] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9dcfcb6 ] LUCENE-7651: Move under the 6.4.1 section. > Javadocs build fails with Java 8 update

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

d3a2ed8487f3934d53f864b092f91966814d4cf7 in lucene-solr's branch refs/heads/branch_6x from [~jpountz] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d3a2ed8 ] LUCENE-7651: Move under the 6.4.1 section. > Javadocs build fails with Java 8 update

[jira] [Comment Edited] (LUCENE-7651) Javadocs build fails with Java 8 update 121

. If we will have a further bugfix release on this branch, we should backport this. Please reopen in that case. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

to mention this change: http://www.oracle.com/technetwork/java/javase/8u121-relnotes-3315208.html It still breaks our previous releases, but we can tell people that its caused by Oracle, not us. > Javadocs build fails with Java 8 update

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

's -bottom parameter. Also update Prettify to latest version to fix Google Chrome issue. # Conflicts: # lucene/CHANGES.txt > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-7651: -- Fix Version/s: 6.4.1 > Javadocs build fails with Java 8 update

Re: Test passes, build fails with "Could not remove temporary path"

Hi, The problem is also the security manager and it's policy file. This is why we have the temp dir in current folder. As there is no easy way to have an absolute path in the policy file, we have it like this. Another way would be to pass a sys prop for the temp directory and add a policy file

Re: Test passes, build fails with "Could not remove temporary path"

Check this out: (FYI this is my test; doesn't exist upstream yet): > ant test -Dtestcase=HeatmapSpatialFieldTest BUILD SUCCESSFUL, 1 minute 40 seconds > ant test-core -Dtestcase=HeatmapSpatialFieldTest BUILD FAILED, 25 seconds So it turns out the "-init-totals" task sets up the temp dir

Re: Test passes, build fails with "Could not remove temporary path"

It's exactly that, actually. We place java.io.tmpdir under ./, so this directory always remains after the tests are done. I filed this issue: https://github.com/randomizedtesting/randomizedtesting/issues/247 But I honestly don't know what the "right" way to fix it is. The runner assumes cwd

Re: Test passes, build fails with "Could not remove temporary path"

No problem at all. I wonder if we (in Lucene) don't point the temp folder under cwd -- we probably do... If so then this is something I didn't give much thought to... special case which should probably be allowed. Check common-build and confirm if this is the case. Dawid On Mon, Jan 23, 2017 at

Re: Test passes, build fails with "Could not remove temporary path"

Thanks very much Dawid. So indeed, the directory in question isn't quite empty; it contains a "temp" directory (that is empty). Off to the next thing to debug Thanks again. ~ David On Mon, Jan 23, 2017 at 7:40 AM Dawid Weiss wrote: > I've committed LUCENE-7653

Re: Test passes, build fails with "Could not remove temporary path"

I've committed LUCENE-7653 which should help you diagnose the problem, David. First, it'll clean the cwd of a forked process before the tests start (something that wasn't done before). Second, it'll report what files remained uncleaned after a run. Hope it'll help. Dawid On Fri, Jan 20, 2017 at

[jira] [Resolved] (LUCENE-7651) Javadocs build fails with Java 8 update 121

) 6.x Fixed for now, please reopen for every bugfix release on any branch that was not yet updated to use this. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

disable all 6.4 branch builds. If we will have a further bugfix release on this branch, we should backport this. Please reopen in that case. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 >

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

's -bottom parameter. Also update Prettify to latest version to fix Google Chrome issue. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

parameter. Also update Prettify to latest version to fix Google Chrome issue. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

://mail.openjdk.java.net/pipermail/javadoc-dev/2017-January/000281.html > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7651 > Proj

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

k Javadocs or build. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7651 > Project: Lucene - Core > Issue

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-7651: -- Attachment: LUCENE-7651.patch Add correct license header to CSS file. > Javadocs build fa

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

? > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7651 > Project: Lucene - Core > Issue Type: Bug >

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

. The used one produced Javascript errors in Chrome, so I updated. I also removed the useless additional language plugin files. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 >

[jira] [Comment Edited] (LUCENE-7651) Javadocs build fails with Java 8 update 121

: This would be my proposal. was (Author: thetaphi): This would be my proposal. Unfortunately, Prettify never worked from local filesystem, so I have to quicly spawn a webserver here... > Javadocs build fails with Java 8 update 121 > --- > >

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-7651: -- Attachment: (was: LUCENE-7651.patch) > Javadocs build fails with Java 8 update

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

it any also works locally. Stupid Javascript! K! > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7651 > Proj

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

from local filesystem, so I have to quicly spawn a webserver here... > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7651 >

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

} {noformat} I checked our sources. We allready append the CSS of prettify to Javadocs's main CSS files. As Java 8 contains also a Javadocs-generated scripts.js file, we could do the same here. I am working on that... > Javadocs build fails with Jav

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833412#comment-15833412 ] Uwe Schindler commented on LUCENE-7651: --- I checked it out, it disallows any

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-7651: -- Labels: Java8 (was: ) > Javadocs build fails with Java 8 update

[jira] [Updated] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-7651: -- Affects Version/s: 6.4 > Javadocs build fails with Java 8 update

[jira] [Assigned] (LUCENE-7651) Javadocs build fails with Java 8 update 121

[ https://issues.apache.org/jira/browse/LUCENE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reassigned LUCENE-7651: - Assignee: Uwe Schindler > Javadocs build fails with Java 8 update

[jira] [Comment Edited] (LUCENE-7651) Javadocs build fails with Java 8 update 121

to "critical", because this also breaks our latest release 6.4, which can't be build from source with Java 8 update 121. was (Author: thetaphi): I se to "critical", because this also breaks our latest release 6.4, which can't be build from source with Java 8 update 121. &g

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

to a separate file helps here. In HTML 5 inline Javascript in HTML files is a no-go. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/bro

[jira] [Commented] (LUCENE-7651) Javadocs build fails with Java 8 update 121

our latest release 6.4, which can't be build from source with Java 8 update 121. > Javadocs build fails with Java 8 update 121 > --- > > Key: LUCENE-7651 > URL: https://issues.apache.org/jira/browse/LUCENE-7

[jira] [Created] (LUCENE-7651) Javadocs build fails with Java 8 update 121

Uwe Schindler created LUCENE-7651: - Summary: Javadocs build fails with Java 8 update 121 Key: LUCENE-7651 URL: https://issues.apache.org/jira/browse/LUCENE-7651 Project: Lucene - Core Issue

Re: Test passes, build fails with "Could not remove temporary path"

Hi David! > I can't find the string "Could not remove temporary path" in our codebase; > maybe it's in randomized-testing? (CC Dawid) I'm not sure how to debug > this... maybe Solr wasn't closed properly? Although this doesn't happen Yes, this message has a source in ANT's unit test runner

Test passes, build fails with "Could not remove temporary path"

-- but not persist it since I don't want/need that. I could share the code if it helps. Any way, my test passes when run via IntelliJ; the test JVM ends normally. But when I run via "ant test-core -Dtestcase=mytestclassname" the test itself passes but the build fails. Right before the

[jira] [Commented] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

(with the added complication that in Java 7 this flag isn't needed). Getting back to trunk, this still applies, any thoughts on this being applied? > Maven build fails for target javadoc:jar on trunk/Java8 > --- > > Key:

[jira] [Updated] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

it. If there are no objections, will go ahead and commit it.. Maven build fails for target javadoc:jar on trunk/Java8 --- Key: LUCENE-6673 URL: https://issues.apache.org/jira/browse/LUCENE-6673 Project

[jira] [Created] (LUCENE-6673) Maven build fails for target javadoc:jar on trunk/Java8

Ramkumar Aiyengar created LUCENE-6673: - Summary: Maven build fails for target javadoc:jar on trunk/Java8 Key: LUCENE-6673 URL: https://issues.apache.org/jira/browse/LUCENE-6673 Project: Lucene

Re: Solr 5 build fails - who do I tell?

: Please provide the details of the errors you’re seeing, and any relevant : environmental details - that would have been higher impact than not : providing details :) when in doubt: file a jira, attach all the details. -Hoss http://www.lucidworks.com/

Solr 5 build fails - who do I tell?

Hi, I did a checkout of the latest 5.0 and the build fails (with ant clean package). With errors from two different JIRAs ports it seems. Should I provide the feedback or do I assume that the Jenkins builds catch this? I can see the build fails, but does not seem to be where mine is? Does

Re: Solr 5 build fails - who do I tell?

) Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode) On Jan 4, 2015, at 11:35 AM, Alexandre Rafalovitch arafa...@gmail.com wrote: Hi, I did a checkout of the latest 5.0 and the build fails (with ant clean package). With errors from two different JIRAs ports it seems. Should

Re: Solr 5 build fails - who do I tell?

of the latest 5.0 and the build fails (with ant clean package). With errors from two different JIRAs ports it seems. Should I provide the feedback or do I assume that the Jenkins builds catch this? I can see the build fails, but does not seem to be where mine is? Does it exercise the same build

Re: Solr 5 build fails - who do I tell?

higher impact than not providing details :) Erik On Jan 4, 2015, at 11:35 AM, Alexandre Rafalovitch arafa...@gmail.com wrote: Hi, I did a checkout of the latest 5.0 and the build fails (with ant clean package). With errors from two different JIRAs ports it seems. Should I provide

Re: Solr 5 build fails - who do I tell?

details :) Erik On Jan 4, 2015, at 11:35 AM, Alexandre Rafalovitch arafa...@gmail.com wrote: Hi, I did a checkout of the latest 5.0 and the build fails (with ant clean package). With errors from two different JIRAs ports it seems. Should I provide the feedback or do I assume

JCC build fails on Mac OS X Mavericks

Hi, I'm having trouble installing JCC. I don't know if this is the right forum, but I figured I would post here, since thishttp://lucene.apache.org/pylucene/mailing-lists.htmlpage said this was the list to post build issues. I'm trying to install JCC as a first step to installing PyLucene. I've

Re: JCC build fails on Mac OS X Mavericks

On Mar 12, 2014, at 4:44, Peter Ganong gan...@gmail.com wrote: Hi, I'm having trouble installing JCC. I don't know if this is the right forum, but I figured I would post here, since thishttp://lucene.apache.org/pylucene/mailing-lists.htmlpage said this was the list to post build issues.

build fails

is it just me? BUILD FAILED C:\work\lucene_dev_fresh\build.xml:23: The following error occurred while execut ing this line: C:\work\lucene_dev_fresh\solr\build.xml:135: The following error occurred while executing this line: C:\work\lucene_dev_fresh\solr\core\build.xml:21: The following error

solr build fails with java 1.5

eclipse I can compile with 1.6 fine, but our production is at 1.5. Any thoughts? -- View this message in context: http://lucene.472066.n3.nabble.com/solr-build-fails-with-java-1-5-tp1756553p1756553.html Sent from the Solr - Dev mailing list archive at Nabble.com

Re: solr build fails with java 1.5

: 1.6 I am using eclipse I can compile with 1.6 fine, but our production is at 1.5. Any thoughts? -- View this message in context: http://lucene.472066.n3.nabble.com/solr-build-fails-with-java-1-5-tp1756553p1756553.html Sent from the Solr - Dev mailing list archive at Nabble.com

Re: solr build fails with java 1.5

suggester component) will it compile with 1.5? -- View this message in context: http://lucene.472066.n3.nabble.com/solr-build-fails-with-java-1-5-tp1756553p1758724.html Sent from the Solr - Dev mailing list archive at Nabble.com

RE: solr build fails with java 1.5

-...@lucene.apache.org Subject: Re: solr build fails with java 1.5 hi yonik, Thanks for reply, I totally understand this. But our prod systems are not going to be on 6 for a year or so. We have solr 1.3 currently and wanted to have suggester component so I was trying to do upgrade and get

[jira] Closed: (LUCENENET-328) Test solution build fails after revision 888204

is uploaded to work on to. So, seeing failing builds from time to time shouldn't be a surprise :-( bq. What was the motivation behind this change? Can't you tolerate a small mistake while people are working with fixing the bugs of Lucene.Net DIGY Test solution build fails after revision 888204

[jira] Updated: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

updated the maven pom template files to reference the right version of BDB-JE which wasn't the case though. I think we should give the maven-repo mirror a chance though. if the build fails to download JARs for contrib/db, just skip its tests

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

the JAR directly is a good savings (it's roughly 1 MB, but the full .zip distribution is roughly 6 MB. I agree we should give maven a shot... hopefully it's more reliable than the direct download we do now. if the build fails to download JARs for contrib/db, just skip its tests

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

it unfortunately touches core stuff :/ simon if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845 URL: https://issues.apache.org/jira/browse/LUCENE-1845

[jira] Assigned: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

[ https://issues.apache.org/jira/browse/LUCENE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-1845: -- Assignee: Michael McCandless (was: Simon Willnauer) if the build fails

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

[ https://issues.apache.org/jira/browse/LUCENE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801409#action_12801409 ] Michael McCandless commented on LUCENE-1845: OK... if the build fails

[jira] Resolved: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

download the JAR from Oracle, let's open a new issue to find a better way to host the jar. if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845 URL: https

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

already replied to the commit mail but mention it here again for completeness We should add a changes.txt entry to notify users that we upgraded the version. simon if the build fails to download JARs for contrib/db, just skip its tests

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

entry to notify users that we upgraded the version. Ahh right -- will do. if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845 URL: https

[jira] Updated: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

: Improvement Reporter: Michael McCandless Assignee: Simon Willnauer Priority: Minor Fix For: 3.1 Attachments: LUCENE-1845.patch, LUCENE-1845.txt, LUCENE-1845.txt, LUCENE-1845.txt, LUCENE-1845.txt Every so often our nightly build fails because

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

{noformat} if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845 URL: https://issues.apache.org/jira/browse/LUCENE-1845 Project: Lucene - Java

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

of this... can we improve the sanity checking to check for lack of existence of the JAR, and then skip everything? if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845

[jira] Updated: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845 URL: https://issues.apache.org/jira/browse/LUCENE-1845 Project: Lucene - Java

[jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests

access, to know it's the nightly build? if the build fails to download JARs for contrib/db, just skip its tests --- Key: LUCENE-1845 URL: https://issues.apache.org/jira/browse/LUCENE-1845

  1   2   >