Skip to content
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

Problems importing :libs:elasticsearch-ssl-config project in Eclipse #38800

Closed
cbuescher opened this issue Feb 12, 2019 · 2 comments
Closed

Problems importing :libs:elasticsearch-ssl-config project in Eclipse #38800

cbuescher opened this issue Feb 12, 2019 · 2 comments
Labels
>bug :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team v7.0.0-rc1 v7.2.0 v8.0.0-alpha1

Comments

@cbuescher
Copy link
Member

cbuescher commented Feb 12, 2019

I have encountered this problem since the libs/ssl-config/ project was added a few weeks ago when trying to import this and dependent subprojects.

Things I did to reproduce:

  • checkout a clean clone of the elasticsearch repo
  • run ./gradlew eclipse (this currently uses Gradle Version 5.1.1)
  • "import existing projects" in Eclipse

Symptoms:

  • the generated libs/ssl-config/src/main/.classpath file is missing a section defining the code "src" directory and an entry for the dependency on the :libs:core project:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="output" path="build-eclipse"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8/"/>
</classpath>
  • as a consequence, the :modules:reindex project is missing classes that should get imported from libs/ssl-config/ (e.g. PemKeyConfig etc..)

Current workaround:

  • after manually adding the "java" directory and adding a project dependency to ":lib:core" to the project, the Eclipse workspace looks fine. This changes the libs/ssl-config/src/main/.classpath file to look like the following:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path="java"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8/"/>
	<classpathentry combineaccessrules="false" kind="src" path="/:libs:core"/>
	<classpathentry kind="output" path="build-eclipse"/>
</classpath>

My Eclipse Version: 2018-12 (4.10.0)

The workaround currently works for me but it would be nice to get this fixed so people (expecially external contributors) can import the project after just running ./gradlwe eclipse.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@alpar-t
Copy link
Contributor

alpar-t commented Feb 19, 2019

Fixed in #39074

@alpar-t alpar-t closed this as completed Feb 19, 2019
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
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 v7.0.0-rc1 v7.2.0 v8.0.0-alpha1
Projects
None yet
Development

No branches or pull requests

6 participants