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

[DOC] Instructions to setup IDEs #3338

Closed
revans2 opened this issue Aug 30, 2021 · 1 comment · Fixed by #3474
Closed

[DOC] Instructions to setup IDEs #3338

revans2 opened this issue Aug 30, 2021 · 1 comment · Fixed by #3474
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@revans2
Copy link
Collaborator

revans2 commented Aug 30, 2021

With some of the more recent changes my IDE setup stopped working and started to show compile errors. This is because I had to select specific maven profiles to make it happy. The only reason I knew this was because I was following along with many of the build changes. We really should have clear instructions about how to set up an IDE, including what maven profiles to enable/disable in specific situations.

@revans2 revans2 added documentation Improvements or additions to documentation feature request New feature or request ? - Needs Triage Need team to review and classify labels Aug 30, 2021
@sameerz sameerz changed the title [FEA] Instructions to setup IDEs [DOC] Instructions to setup IDEs Aug 31, 2021
@sameerz sameerz removed ? - Needs Triage Need team to review and classify feature request New feature or request labels Aug 31, 2021
@sameerz
Copy link
Collaborator

sameerz commented Aug 31, 2021

We need to update https://github.com/NVIDIA/spark-rapids/blob/branch-21.10/docs/dev/README.md ( which gets displayed at https://nvidia.github.io/spark-rapids/developer-overview/ ) after we complete the Spark 3.2 shim work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants