m2e doesn't systematically use the jdk associated with the project to run mojos leading to inconstancies

[andre-doherty]

hello,

Following the #988 i have investigated on the com.sun.xml.ws:jaxws-maven-plugin behavior.
As far as i understand, the m2e plugin doesn't rely on the maven toolchain.
This is perfectly ok, however it appears that the jaxws-maven-plugin is not run using the project associated jdk but instead the eclipse jdk.
As the wsgen goal implies java source compilation and so bytecode generation, this leads to runtime errors when the project jdk and testing process are not aligned with the eclipse jdk.

You may want to use the following sample :
https://github.com/andre-doherty/sample-jaxws

And monitor the bytecode using this command :
watch -d -n 1 'find target -type f -name "GetAll*" | xargs file'

Using :
Eclipse.org Eclipse Platform 4.34.0.v20241120-1800 org.eclipse.platform
Eclipse.org - m2e M2E Maven Integration for Eclipse Core 2.7.0.20241126-1642 org.eclipse.m2e.feature

André