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

Update scalablyTypedImportTask to also check for IVY_HOME #36

Closed

Conversation

imdaveho
Copy link

@imdaveho imdaveho commented Jan 8, 2025

This enables the Task to also look for IVY_HOME if the user has specified it. If not, it still defaults to ~/.ivy2. It still looks for any Java declaration flags -Divy.home=<...> if passed in first.

This was first opened by #35 and adds the suggestion for making this change additive rather than replacing the original sys.props check. Deleted the other one, because I was using github.com to make the edits, rather than on my machine.

This enables the Task to also look for IVY_HOME if the user has specified it. If not, it still defaults to ~/.ivy2. It still looks for any Java declaration flags `-Divy.home=<...>` if passed in first.
@imdaveho
Copy link
Author

imdaveho commented Jan 9, 2025

@lolgab -- this was following your suggestion in the other PR that I closed previously. Any chance this could be merged?

@imdaveho
Copy link
Author

imdaveho commented Jan 9, 2025

Since I'm new to javaland, is the preferred option not to use environment variables and directly set properties to the JVM like with -Divy.home? If so, I can close this PR

@imdaveho imdaveho closed this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant