[JENKINS-52024] Can't compile/test under Java 10/11 with mvn

[jenkins-infra-bot]

Sample error from workflow-support-plugin:

[ERROR] java.nio.file.NoSuchFileException:$GIT_REPO/target/classes/META-INF/annotations/hudson.Extension

(Where $GIT_REPO is the actual folder holding the code). 

---

Originally reported by svanoort, imported from: Can't compile/test under Java 10/11 with mvn

• assignee: oleg_nenashev
• status: Resolved
• priority: Minor
• component(s): plugin-pom
• label(s): java10, java10_hackathon, java11
• resolution: Fixed
• resolved: 2018-09-26T08:51:26+00:00
• votes: 0
• watchers: 5
• imported: 20260108-221235

Raw content of original issue

Sample error from workflow-support-plugin:

[ERROR] java.nio.file.NoSuchFileException:$GIT_REPO/target/classes/META-INF/annotations/hudson.Extension

(Where $GIT_REPO is the actual folder holding the code). 

• environment: Java 10 as JAVA_HOME for Maven

[jenkins-infra-bot]

• Remote links associated with this issue:

  • sezpoz PR 13
  • core PR 3516
  • Core PR#​3635. master branch

[jenkins-infra-bot]

svanoort:

• Original comment link
• Raw content of original comment:

  Annotations folder is indeed empty.   
  
  I wonder if we might be seeing some flavor of https://issues.apache.org/jira/browse/MCOMPILER-310
  

Annotations folder is indeed empty.   

I wonder if we might be seeing some flavor of https://issues.apache.org/jira/browse/MCOMPILER-310

[jenkins-infra-bot]

svanoort:

• Original comment link
• Raw content of original comment:

  Per this issue Java 9: java.annotations.common has been renamed to java.xml.ws.annotation mapstruct/mapstruct#1382 we tried using:  MAVEN_OPTS="--add-modules java.xml.ws.annotation"  to support annotations...
  
  and it still failed. 
  

Per this issue mapstruct/mapstruct#1382 we tried using:  MAVEN_OPTS="--add-modules java.xml.ws.annotation"  to support annotations...

and it still failed. 

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  I updated to the latest Maven Compiler just in case, no luck
  

I updated to the latest Maven Compiler just in case, no luck

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  There are org.kohsuke.accmod.Restricted org.kohsuke.stapler.export.ExportedBean in the annotations directory tho. Kinda moving forward
  

There are org.kohsuke.accmod.Restricted org.kohsuke.stapler.export.ExportedBean in the annotations directory tho. Kinda moving forward

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  sezpoz update in the core resolves the issue, but you always have to run with newer Jenkins Core dependency to get it running
  

sezpoz update in the core resolves the issue, but you always have to run with newer Jenkins Core dependency to get it running

[jenkins-infra-bot]

svanoort:

• Original comment link
• Raw content of original comment:

  oleg_nenashev I swear I had this working after the PRs attached...
  

oleg_nenashev I swear I had this working after the PRs attached...

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  svanoort I actually compile on Java 11 so my mileage may vary (spoiler: it hurts)
  

svanoort I actually compile on Java 11 so my mileage may vary (spoiler: it hurts)

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  Addressed in 2.143.
  

Addressed in 2.143.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  Solution in my case (and I believe the general case) to compile with Java 11 needs to use Jenkins version 2.164 or later (slightly older versions can compile with Java 11, Jenkins 2.150 cannot compile with Java 11).
  
  My command line to compile with Java 11 was:
  
  
  $ java -version
  openjdk version "11.0.2" 2019-01-15
  OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
  OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
  $ mvn --version
  Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T18:41:47Z)
  Maven home: /home/jagent/tools/apache-maven-3.6.0
  Java version: 11.0.2, vendor: Oracle Corporation, runtime: /mnt/xvdba/home/jagent/tools/jdk-11.0.2
  Default locale: en_US, platform encoding: UTF-8
  OS name: "linux", version: "2.6.32-754.6.3.el6.x86_64", arch: "amd64", family: "unix"
  $ mvn -Djenkins.version=2.164 clean install
  
  
  

Solution in my case (and I believe the general case) to compile with Java 11 needs to use Jenkins version 2.164 or later (slightly older versions can compile with Java 11, Jenkins 2.150 cannot compile with Java 11).

My command line to compile with Java 11 was:

$ java -version
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
$ mvn --version
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T18:41:47Z)
Maven home: /home/jagent/tools/apache-maven-3.6.0
Java version: 11.0.2, vendor: Oracle Corporation, runtime: /mnt/xvdba/home/jagent/tools/jdk-11.0.2
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-754.6.3.el6.x86_64", arch: "amd64", family: "unix"
$ mvn -Djenkins.version=2.164 clean install