Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-05 Thread via GitHub
dweiss closed issue #14600: Apache jenkins nodes use java 24-ea URL: https://github.com/apache/lucene/issues/14600 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscrib

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
dweiss commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2846399752 I see this in the output of [1]: ``` Eclipse Temurin OpenJDK Runtime Environment 24.0.1+9 ``` Looks ok to me. I'd wait until Gavin responds on the jira issue before en

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2845772648 Looks like lucene-solr-1 works correct. I triggered a job and it succeeded. Not sure about the other nodes. Uwe -- This is an automated message from the Apache Git Servi

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844679676 Here is my idea: #1460#14595 I think this is simplest. It works fine, we can try it also on ASF Jenkins. -- This is an automated message from the Apache Git Service. To

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844660289 Hi, yes and no. From the mrjars discussion I know that some people don't like it when Gradle downloads their JDK. For the regenerate task in the mrjar (or better said) vector cod

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
dweiss commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844619480 Another alternative is to embrace toolchains to download the base jdk for us, letting gradle run with whatever it is compatible with. Much like with the current hack for mrjars. --

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844551272 P.S.: Release candidate builds don't have `pre()` set, they behave like normal GA releases. In fact, they will be released later as GA. -- This is an automated message from the

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844545708 We could also disallow EA versions for Gradle in general. Of course you can still run the tests and compilation with EA versions using `RUNTIME_JAVA_HOME`. -- This is an automa

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844540507 Hi, maybe we should improve the Java version check on Gradle startup a bit and disallow EA versions there, if the boot JDK major version is equal to minimum requirements. Some

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
dweiss commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844498810 I don't understand it either. Let's just wait. We have reasonable coverage with your jenkins and gh. -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844378552 I agree with this! From the mesage on the INFRA issue it seems that he did not yet update Jenkins JVMs, he just mentioned why lucene-solr-3 and -4 have no JDK 24 ("because

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
dweiss commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844352546 It didn't work and I don't think it makes sense to invest any more time in this. I've reverted the hack and turned off jenkins builds until the infrastructure is up-to-date. -- Th

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
dweiss commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844347781 I don't think the workaround will work at all. Let's see. I will revert the hack before closing this issue. -- This is an automated message from the Apache Git Service. To respond

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844247399 > Specifically, Oracle OpenJDK 64-Bit Server VM 24-ea+2-133. Thats the oldest one and is basically Java 23 Do you know why the JDK versions are so outdated espec

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
uschindler commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844243674 Oh thats horrible. I hope we can remove that workaround commit soon! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[I] Apache jenkins nodes use java 24-ea [lucene]

2025-05-01 Thread via GitHub
dweiss opened a new issue, #14600: URL: https://github.com/apache/lucene/issues/14600 ### Description Specifically, Oracle OpenJDK 64-Bit Server VM 24-ea+2-133. This causes build failures on main because #14597 requires class builder API and it's declared as a feature in ea. #

Re: [I] Apache jenkins nodes use java 24-ea [lucene]

2025-04-30 Thread via GitHub
dweiss commented on issue #14600: URL: https://github.com/apache/lucene/issues/14600#issuecomment-2844219216 Depends on #14590. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific commen