Ok, it seems that this is currently a missing feature and it may be fixed in the next version:
- http://stackoverflow.com/questions/40783030/jenkins-artifactory-plugin-not-detecting-my-compiler-during-maven-build - https://www.jfrog.com/jira/browse/HAP-848 Am Freitag, 2. Dezember 2016 21:22:46 UTC+1 schrieb Daniel: > > Hi together, > > I am currently setting up a build pipeline that uses the artifactory maven > plugin to build and publish artifacts. > > The following examples were a good start: > > - > > https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+-+Working+With+the+Pipeline+Jenkins+Plugin > - > > https://github.com/JFrogDev/project-examples/blob/master/jenkins-pipeline-examples/maven-example/Jenkinsfile > > However I wasn't able to define the Java Version which should be used to > run maven. > > Setting env.JAVA_HOME and env.PATH works fine for sh 'java -version' but > it has no effect for the artifactory maven plugin. > > Any hints are greatly appreciated. > > Thanks, Daniel > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e71faf6e-c355-48fd-80ee-c147693e6b97%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
