Integration Tests with Docker and Testcontainers To further verify the compatibility and optimization for various other tools for Apple's M1, checkout out isapplesiliconready. Only try to get the 圆4 build running if there's no arm64 build available (yet).
Rule one: Whenever there's a native arm64 build of any development tool for the M1, go for it. But having worked with it for almost a year now, many have been continuously fixed.Īll other development tools that we use on a daily basis either provide an arm64 build or the emulated 圆4 version works fine: IntelliJ IDEA, Visual Studio Code, Eclipse, Slack, Notion, Docker for Mac, Spotify, Firefox, Microsoft Teams, Postman. In the early days, there were some minor issues. Installing a recent Docker for Mac version comes with Apple M1 support. However, we may run into issues and/or won't get the expected performance. With Apple's Rosetta 2 emulation, we can also try to work with an 圆4 JDK build. For managing different Java versions, sdkman or jEnv is an excellent option.įor those lucky developers that have the chance to work and experiment with the GraalVM, the support for Apple M1 has also landed. The brew formula for openjdk is also installing a compatible Apple M1 JDK build. Eclipse Temurin (Adoptium project, former AdoptOpenJDK).28 + 13 - CA ( build 17 + 35 - LTS, mixed mode, sharing )Īpart from the Azul Zulu JDK, many other JDK vendors have followed and now offer an arm64 build: Once we've downloaded and installed a compatible JDK build, we have the baseline for our Java development for our Apple M1:
There's no difference in the installation process of a JDK compared to an 圆4 Mac. While searching for a arm64 compatible JDK back in 2021, the Azul Zulu JDK build popped up first. The first thing we install as Java developers on a new machine is a JDK. I'll refer to the traditional Intel/AMD processors as 圆4 (you may find the following synonyms: x86_64, amd64).
Note: Throughout this article, both arm64 or aarch64 refer to the Apple M1 chip. This article will share my initial pitfalls when working with the Apple M1 and a collection of valuable tricks and workarounds for developing and testing Java applications. To solve those problems (not my main intent, but I told myself so) and experience if that processor is really that fast, I decided to buy the MacBook Pro. I was first shocked to encounter hardware incompatibilities in 2021. I had my first contact with the Apple M1 when one of my course students raised an issue that the build doesn't pass on Apple's new flagship laptop. It's been almost a year since I've bought the MacBook Pro M1 ( arm64 processor) for my daily Java development as a freelance consultant.
0 kommentar(er)
