Skip to content

eclipse import broken #76373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nik9000 opened this issue Aug 11, 2021 · 4 comments · Fixed by #76382
Closed

eclipse import broken #76373

nik9000 opened this issue Aug 11, 2021 · 4 comments · Fixed by #76382
Labels
>bug :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team

Comments

@nik9000
Copy link
Member

nik9000 commented Aug 11, 2021

Importing Elasticsearch into eclipse fails as of sometime this morning I think. The error message can be reproduced without eclipse with:

$ ./gradlew tasks
Directory '/usr/lib/jvm/java-13-openjdk' (environment variable 'JAVA13_HOME') used for java installations does not exist
=======================================
Elasticsearch Build Hamster says Hello!
  Gradle Version        : 7.1.1
  OS Info               : Linux 5.12.10-arch1-1 (amd64)
  JDK Version           : 16.0.1 (Oracle)
  JAVA_HOME             : /home/nik9000/Bin/jdk-16.0.1
  Random Testing Seed   : 68EFFB12606AAA97
  In FIPS 140 mode      : false
=======================================
> Task :tasks FAILED

FAILURE: Build failed with an exception.

* Where:
Build file '/home/nik9000/Code/Elastic/elasticsearch/modules/lang-painless/build.gradle' line: 66

* What went wrong:
Execution failed for task ':tasks'.
> Could not create task ':modules:lang-painless:apiJavadoc'.
   > Could not get unknown property 'classpath' for configuration ':modules:lang-painless:spi' of type org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.

@nik9000 nik9000 added >bug :Delivery/Build Build or test infrastructure labels Aug 11, 2021
@elasticmachine elasticmachine added the Team:Delivery Meta label for Delivery team label Aug 11, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@nik9000
Copy link
Member Author

nik9000 commented Aug 11, 2021

This looks to have been caused by #76288. Reverting to just before that commit seems to fix it.

@nik9000
Copy link
Member Author

nik9000 commented Aug 11, 2021

@rjernst I think modules:lang-painless:apiJavadoc is broken - the task doesn't properly configure itself any more. Do you think it'd be useful to run that task when we build painless?

@rjernst
Copy link
Member

rjernst commented Aug 11, 2021

@nik9000 We run it as part of assemble.
@mark-vieira Does assemble not run with CI?

rjernst added a commit to rjernst/elasticsearch that referenced this issue Aug 11, 2021
The javadoc generation for painless api classes was broken by a recent
commit. This commit fixes it by correct the classpath used to run the
javadoc task. Additionally, the task is added to `check` to ensure it
runs with CI.

closes elastic#76373
elasticsearchmachine pushed a commit that referenced this issue Aug 11, 2021
The javadoc generation for painless api classes was broken by a recent
commit. This commit fixes it by correct the classpath used to run the
javadoc task. Additionally, the task is added to `check` to ensure it
runs with CI.

closes #76373
rjernst added a commit to rjernst/elasticsearch that referenced this issue Aug 11, 2021
The javadoc generation for painless api classes was broken by a recent
commit. This commit fixes it by correct the classpath used to run the
javadoc task. Additionally, the task is added to `check` to ensure it
runs with CI.

closes elastic#76373
elasticsearchmachine pushed a commit that referenced this issue Aug 11, 2021
The javadoc generation for painless api classes was broken by a recent
commit. This commit fixes it by correct the classpath used to run the
javadoc task. Additionally, the task is added to `check` to ensure it
runs with CI.

closes #76373
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants