suresh
07/30/2025, 9:45 PMAMPER_JAVA_HOME
env variable allows for an override, Amper currently defaults to downloading JBR 21. Would it be possible for Amper to leverage an existing, compatible JDK by default?joffrey
07/30/2025, 9:52 PMsuresh
07/30/2025, 9:56 PMuser so there is no real reason to override this.In enterprise and CI/CD environments, it’s often better to use the existing JDK, and sometimes we’re restricted to downloading resources only from Maven Central.
joffrey
07/30/2025, 10:59 PMsuresh
07/31/2025, 12:07 AMwe’re not talking about the JDK toolchain, but the Amper runtimeThanks, that’s clear. We still need to download the bootstrapping JDK (as per the current
amper/amper.bat
scripts), and we might run into access issues. It’d be good to have a fallback option, like using an existing, compatible JDK as the Amper runtime. Gradle does that. (I am not saying we should following the gradle route 🙂 )joffrey
07/31/2025, 10:54 AMjoffrey
07/31/2025, 10:55 AMsuresh
07/31/2025, 5:22 PMnative GraalVM image|Are there any plans to create native image? It will be interesting to see how the new plugins will play out in the native image world.
Amper distribution itselfMake sense.
joffrey
08/01/2025, 12:31 PMAre there any plans to create native image? It will be interesting to see how the new plugins will play out in the native image world.No very short terms plans, but we're open to the idea. With project Crema it should be possible to deal with plugins
suresh
08/22/2025, 12:10 AM