Before creating a feature request make sure the suggestion fit within our principles
Is your feature request related to a problem? Please describe.
fvm flutter config --jdk-dir sets the JDK path globally. and without it flutter gives preference to the configured Android SDK/JDK path over the system JAVA_HOME.
When working on multiple projects that require different Java versions (e.g., an older project needing JDK 11 and a newer one needing JDK 17 or newer), running the config command in one project breaks the build environment for all others. FVM currently provides an isolated Flutter SDK environment, but the underlying Java requirement remains a "global leak" that requires manual intervention every time I switch projects.
Describe the solution you'd like
I would like FVM to manage the JDK path on a per-project basis, effectively "localizing" the --jdk-dir setting.
Describe alternatives you've considered
- mainly manual toggling. Running fvm flutter config --jdk-dir every time I switch folders, which is tedious and prone to error.
- changing JAVA_HOME, but without jdk-dir flutter ignores the environment variable and defaults to the android SDK version
Additional context
This would complete the "project sandbox" experience. Currently, FVM handles the SDK perfectly, but the Android build toolchain remains "leaky" because of how Flutter stores its JDK path globally.
Before creating a feature request make sure the suggestion fit within our principles
Is your feature request related to a problem? Please describe.
fvm flutter config --jdk-dir sets the JDK path globally. and without it flutter gives preference to the configured Android SDK/JDK path over the system JAVA_HOME.
When working on multiple projects that require different Java versions (e.g., an older project needing JDK 11 and a newer one needing JDK 17 or newer), running the config command in one project breaks the build environment for all others. FVM currently provides an isolated Flutter SDK environment, but the underlying Java requirement remains a "global leak" that requires manual intervention every time I switch projects.
Describe the solution you'd like
I would like FVM to manage the JDK path on a per-project basis, effectively "localizing" the --jdk-dir setting.
Describe alternatives you've considered
Additional context
This would complete the "project sandbox" experience. Currently, FVM handles the SDK perfectly, but the Android build toolchain remains "leaky" because of how Flutter stores its JDK path globally.