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

Add new instruction for Eclipse #54894

Merged
merged 7 commits into from
Apr 8, 2020
Merged

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Apr 7, 2020

These work much better.

These work *much* better.
@nik9000 nik9000 added >docs General docs changes :Delivery/Build Build or test infrastructure v8.0.0 labels Apr 7, 2020
@nik9000 nik9000 requested review from costin and cbuescher April 7, 2020 14:00
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (>docs)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

Copy link
Member

@cbuescher cbuescher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, great setting-up tutorial. I left a few comments where I can imagine ppl might have questions for discussion.
I also had an issue initially importing the blank "Existing Gradle Project", got weird "Could not run phased build action using Gradle distribution ‘https://services.gradle.org/distributions/gradle-6.3-all.zip’.”" errors that I couldn't immediately action upon. The Eclipse log later pointed to a wrong java version (12) used for out build that was apparently picked up because I still run my Eclipse with Java 12. I manually set the "Java Home" gradle uses under Preferences>Gradle>Advanced Options. Maybe you can also do that in the import dialogue, I didn't check. Its probably worth either mentioning that in some sort of FAQ or point out that Eclipse should be run with at least Java 13?


- Select **Window > Preferences**
- Select **Java > Compiler > Building**
- Set **Circular dependencies** to **Warning**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe mention the setting is under "Build Path Problems". I know where they are because I had to set them so often but new users might need that extra bit of info.

- Select **Window > Preferences**
- Select **Java > Compiler > Building**
- Set **Circular dependencies** to **Warning**
- Apply that and let the build spin away for a while
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had to do the Refresh/Cleanup dance once but I guess that's what everybody expects?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think accepting this change will prompt you to let it rebuild. I didn't do it when writing the instructions but it is what I remember. If you need to refresh or clean up we should so. I mostly don't have to do that though.

CONTRIBUTING.md Outdated
org
java
javax
static *
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't exactly sure what this mean. I chose "New Staic" with a "*" pattern. Maybe worth elaborating?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

++

@nik9000
Copy link
Member Author

nik9000 commented Apr 7, 2020

@cbuescher, could you have another look?

@nik9000
Copy link
Member Author

nik9000 commented Apr 7, 2020

@elasticmachine update branch

@@ -0,0 +1,8 @@
#Organize Import Order
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this is an eclipse generated file. Maybe it would make sense to mention this in this file somewhere to know what its used for?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

++

@cbuescher
Copy link
Member

@nik9000 thanks for the updates, I like the setup guide a lot so far. One thing I'm still thinking about with regards to my previous comment in #54894 (review) is whether it would make sense to include a word or two about required jvm version to run gradle (and what to expect if you have a lower version). Maybe you have some ideas about that?
I'd be fine to get this in as is though and later iterate on improvements, but I think at least one other Eclipse user should try this guide from scratch, a lot of small bumps can be identified by this.

- Select **Existing Gradle Project**
- Select **Next** then **Next** again
- Set the **Project root directory** to the root of your elasticsearch clone
- Click **Finish**

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me an immediate finish did not produce the projects, I had to go through all Next stages and click the final Finish.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

Copy link
Contributor

@astefan astefan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome. Worked for me way better than my previous setup. Thank you for putting these together. Tested this with a fresh Eclipse 2020-3 install, fresh project checkout and JDK 13.0.2.

Copy link
Member

@cbuescher cbuescher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nik9000
Copy link
Member Author

nik9000 commented Apr 8, 2020

run elasticsearch-ci/bwc

@nik9000
Copy link
Member Author

nik9000 commented Apr 8, 2020

run elasticsearch-ci/default-distro

@nik9000 nik9000 merged commit 6fd6895 into elastic:master Apr 8, 2020
@nik9000 nik9000 mentioned this pull request Apr 8, 2020
7 tasks
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
@jakelandis jakelandis removed the v8.0.0 label Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure >docs General docs changes Team:Delivery Meta label for Delivery team v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants