![]() There's also an argument here for (I think?) us all broadly being advocates of open source and if we can nudge people from a closed-source solution to a drop-in open source replacement that feels like a win. This would be a nice step in that direction. Plus I think it's best if you suggest users run the exact same JDK that you're running on the CI servers.Īnd, as a Java developer and advocate, I think it'd be great if the entire Java-using community moved towards thinking of AdoptOpenJDK as the default, "obvious" choice for a JDK. My $0.02 would be that we eventually consider renaming the adoptopenjdk cask to java (and even moreso same for adoptopenjdk8 to java8) to preserve compatibility with what "we" prioritise. And add them to be managed by jenv as usual. Then you can install the version (s) you like: brew install -cask java7 brew install -cask java6. Then you can look at all the versions available: brew search java. What about the depends_on_java caveats? Should they start recommending AdoptOpenJDK instead? Add the homebrew/cask-versions tap to homebrew using: brew tap homebrew/cask-versions.I don't see any requirement from the Homebrew side to do that but have no arguments for or against it. brew cask install java will still work and brew cask install java8 has been broken by changes beyond our control. > Auto-updated Homebrew Updated 1 tap (adoptopenjdk/openjdk). I support this but one thing on my mind is CI automation that installs a formula that would previously install the java package as a dependency will no longer do that I don't understand why you've reached than conclusion considering this is just changing a text string specifying our recommendation. homebrew-openjdk git:(path) brew cask install adoptopenjdk8 Updating Homebrew. Like above, I’m going to follow up in Homebrew/homebrew-cask#57387. Should we keep the java casks, or being proactive about Oracle rename them to oracle-java, meaning no cask will ever again be the Java but a Java?.How should we deal with those? If they wish to remain independent but we still want those casks in the main repos, I’m willing to build a script/bot that will pull their versions daily. AdoptOpenJDK has an external tap, meaning we’ll have some duplication efforts.However, due to a recent update on the availability of. I’m going to follow up in Homebrew/homebrew-cask#57387 as I think that’s where the topic fits best. Step 1 (Optional): Install Homebrew Step 2: Install Java 8 Step 3: Install Scala Step 4: Install Spark Step 5: Install pySpark Step 6: Modify your bashrc Step 7: Launch a Jupyter Notebook I have encountered lots of tutorials from 2019 on how to install Spark on MacOS, like this one. You mean, add them as casks (to homebrew-cask-versions)? We absolutely need to discuss that and make a decision. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |