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

Version of the javac compiler cannot be determined corretly when custom compiler executable is set #408

Open
luktom opened this issue Sep 9, 2024 · 1 comment
Labels

Comments

@luktom
Copy link

luktom commented Sep 9, 2024

Hi,

we are using a javac wrapper for compiling our project, its doing some stuff and delegates the compilation to javac. The wrapper is set in the 'executable' property of the maven-compiler-plugin. The wrapper needs some custom arguments provided via the CLI arguments of compiler executable.

After updating the maven-compiler-plugin our project fails to compile, the root cause was introduced in the #357. The 'JavacCompiler#getOutOfProcessJavacVersion' invokes the compiler executable only with '-version' parameter, but without any custom parameters defined in the 'CompilerConfiguration#customCompilerArguments'. Thus our wrapper and possibly all custom executables are failing to run properly due to missing custom arguments.

@cmconti
Copy link

cmconti commented Oct 16, 2024

i'm still experimenting, but this change also appears to break setting up a toolchain for jdk 1.4 (don't ask) since that javac doesn;t support -version as a param

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants