[ 
https://issues.apache.org/jira/browse/LUCENE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160639#comment-17160639
 ] 

Uwe Schindler edited comment on LUCENE-9433 at 7/19/20, 11:30 AM:
------------------------------------------------------------------

Hi Erick: As said before. Please don't push this unless we havea possibility to 
run With Java EA releases. With Gradle this does not work out of the box. If 
you push this, at least Policeman Jenkins builds are dead mainly.

To make this work we first need either one of the following:
- Ability to pass a "test runner" JDK home dir (this is what Elasticsearch is 
doing). The backside of this is that we can't test compilation with later Java 
versions - which is a pity, but I could live with it. Basically we need some 
"{{-Dtestrunner.jdk=/path/to/javahome}}" property and implementation in the 
test runner. In that case I could theoretically configure the Jenkins jobs to 
run gradle with JDK 11 and just use "Tool Environment" plugin to pass the 
property to gradle.
- Or the f*cking Gradle is finally fixed to not fail in their Groovy 
integration whenever some JDK version updates. I know from Alan Bateman of JDK 
that the JDK people tried several times to contact Gradle people to fix the 
long standing issue (e.g., removal of shading of ASM and removal  of useless 
reflection in Groovy/Gradle to "hack" the JDK internals), but they get no 
response. Also Gradle refuses to take place in the JDK early release testing, 
there's absolutely no communication. We spent about one and a half hour on the 
last OpenJDK committers meeting in Brussels (was very funny, all major 
opensource projects had a representative there, but nobody from Groovy or 
Gradle accepted the invistation for discussion). So don't expect this to be 
ever fixed. The Gradle cooperation seems to have no interesting in fixing this, 
instead they are just arguing against Groovypeople (who also don't want to fix 
this). Groovy also does not really talk to OpenJDK people (both sides are 
somehow in conflict).


was (Author: thetaphi):
Hi Erick: As said before. Please don't push this unless we havea possibility to 
run With Java EA releases. With Gradle this does not work out of the box. If 
you push this, at least Policeman Jenkins builds are dead mainly.

To make this work we first need either one of the following:
- Ability to pass a "test runner" JDK home dir (this is what Elasticsearch is 
doing). The backside of this is that we can't test compilation with later Java 
versions - which is a pity, but I could live with it. Basically we need some 
"{{-Dtestrunner.jdk=/path/to/javahome}}" property and implementation in the 
test runner. In that case I could theoretically configure the Jenkins jobs to 
run gradle with JDK 11 and just use "Tool Environment" plugin to pass the 
property to gradle.
- Or the f*cking Gradle is finally fixed to not fail in their Groovy 
integration whenever some JDK version updates. I know from Alan Bateman of JDK 
that the JDK people tried several times to contact Gradle people to fix the 
long standing issue (e.f., shading ASM and using reflection in Groovy/Gradle), 
but they get no response. Also Gradle refuses to take place in the JDK early 
release testing, there's absolutely no communication. So don't expect this to 
be ever fixed. The Gradle cooperation seems to have no interesting in fixing 
this, instead they are just arguing against Groovypeople (who also don't want 
to fix this). Groovy also does not really talk to OpenJDK people (both sides 
are somehow in conflict).

> Remove Ant support from trunk
> -----------------------------
>
>                 Key: LUCENE-9433
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9433
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Items that may need to be addressed:
>  * Testing with OpenJDK early access releases
>  * Mavenizing
>  * Test speed (?)
>  * check build for ref guide
>  * Update Confluence
>  * Update Jenkins to not try to run ant anything
>  * make an eclipse target



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to