Run into the same exact problem while running sonar analysis with java-9.
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
Maven home: D:\java\maven\3.5.0\bin\..
Java version: 9, vendor: Oracle Corporation
Java home: D:\java\jdk\1.9.0_181
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
...
[INFO] --- sonar-maven-plugin:3.3.0.603:sonar (default-cli) @ _test ---
...
[INFO] SonarQube version: 6.5.0
...
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project
maven:sonar-maven-plugin:3.3.0.603:sonar: javax/xml/bind/JAXBException
Same build still works fine with java-8.
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
Maven home: D:\java\maven\3.5.0\bin\..
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: D:\java\jdk\1.8.0_131\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
...
[INFO] --- sonar-maven-plugin:3.3.0.603:sonar (default-cli) @ _test ---
...
[INFO] SonarQube version: 6.5.0
...
[INFO] BUILD SUCCESS
I see same behavior with javax.javaee-api 6.0 7.0 or 8.0 thus problem seems to be not related to project dependencies.
Older org.sonarsource.scanner.maven.sonar-maven-plugin 3.2 version of plugin produces same result thus problem is not related to newer 3.3.0.603 plugin version.
Run only with maven 3.5.0.
Just for sake of it successfully tested with 1.8.0_144 in addition to 1.8.0_131.
Exact version of SonarQube is 6.5.0.27846.
Just a suggestion: make sure you are actually running java-8.
mvn -v