You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows 10 with Git Bash
Reproduction steps
Have JDK11 early in PATH as the default
Run mvn archetype:generate -Dfilter=io.jenkins.archetypes:
Select 1. empty-plugin
Select a name etc. (in my case N for defaults and picked all the group names etc.)
Expected Results
Successful generation (as it does happen when I export JAVA_HOME="C:\Program Files\Eclipse Adoptium\jdk-17.0.3.7-hotspot")
Actual Results
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate (default-cli) on project standalone-pom: could not access constructor: private java.io.File(java.lang.String,java.io.File) with arguments: [Jenkinsfile, C:\continuous-integration\jsl-types] reason: java.lang.IllegalAccessException: class org.codehaus.groovy.reflection.CachedConstructor cannot access a member of class java.io.File (in module java.base) with modifiers "private" -> [Help 1]
Anything else?
Originally PATH pointed to JDK11, even though MVN thought differently - that it has JDK17:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows 10 with Git Bash
Reproduction steps
mvn archetype:generate -Dfilter=io.jenkins.archetypes:
1. empty-plugin
N
for defaults and picked all the group names etc.)Expected Results
Successful generation (as it does happen when I
export JAVA_HOME="C:\Program Files\Eclipse Adoptium\jdk-17.0.3.7-hotspot"
)Actual Results
Anything else?
Originally
PATH
pointed to JDK11, even though MVN thought differently - that it has JDK17:Exporting JDK17 JAVA_HOME and PATH explicitly did work around the issue:
Still, as JDK11 is supposed to be a supported baseline for Jenkins, I think this is an issue to address (or document at least).
The text was updated successfully, but these errors were encountered: