The problem with extensions is different. And I don't think we'll fix it. The problem .mvn and usage of -f is a maven bug fixed in 3.5.0 or 3.5.1
Le mar. 6 juin 2017 à 19:36, Pascal <pascal.gr...@gmail.com> a écrit : > The existing bug to support core extensions: > https://issues.jenkins-ci.org/browse/JENKINS-30058 > > As I said, the only solution so far is to use a Freestyle project. You can > find more details in the bug comments. > > Pascal > > > 2017-06-06 19:27 GMT+02:00 Pascal <pascal.gr...@gmail.com>: > > > Hello, > > > > I fear you have done everything correctly and the issue is with the > > Jenkins Maven plugin. There is already a bug report in the Jenkins Maven > > Plugin, but it's hard to find. If I recall how to find it, I will post it > > here. > > > > Unfortunately, it does not look like an easy bug, so you cannot use the > > "Maven" Job type in Jenkins together with the .mvn folder feature. > However, > > what you can do is create a Freestyle Job and add a build step "Call > Maven > > goals". > > > > Cheers, > > > > Pascal > > > > > > 2017-06-06 18:13 GMT+02:00 Eric B <ebenza...@gmail.com>: > > > >> Hi, > >> > >> I'm cross posting this to StackOverflow ( > >> https://stackoverflow.com/q/44394234/827480) b/c I'm not truly > convinced > >> this is a maven question per say. Rather I think it is more something > due > >> to my Jenkins job config that is causing some issues, but I am hoping > that > >> maven users here may have encountered this in Jenkins as well. Either > >> that, or maybe someone can point out that I'm using the .mvn folder > >> incorrectly. > >> > >> Essentially, I have a multi-module maven project that is set up as: > >> > >> |.mvn > >> \-maven.config > >> \-jvm.config > >> |superpom > >> \-pom.xml (main project parent pom, includes module defns) > >> |module1 > >> \-pom.xml (parent points to ../superpom/pom.xml) > >> \src > >> \... > >> |module2 > >> \-pom.xml (parent points to ../superpom/pom.xml) > >> \src > >> \... > >> > >> My maven.config file is defined as: > >> > >> -Dsign.alias=cert > >> -Dsign.storepass=changeit > >> -Dsign.keypass=changeit > >> -Dcheckstyle.skip=true > >> -Dcobertura.skip=true > >> -Dpmd.skip=true > >> -DskipTests=true > >> -DdatabaseUrl=jdbc:sqlserver://localhost:1433;databaseName=TEMP > >> -DuserName=test > >> -Dpassword=test > >> -f superpom/pom.xml > >> > >> If I run my maven build from the command line, everything builds as > >> expected. ie: > >> > >> [project]$ mvn clean install > >> > >> However, when I configure my jenkins job, it is failing as though it is > >> not > >> seeing/reading the .mvn/ folder/files. In fact, to be honest, I'm not > >> entirely sure how to configure my maven project in Jenkins. If I leave > my > >> ROOT pom definition as blank, then Jenkins complains it doesn't have a > >> pom.xml file. > >> > >> If I specify my root pom as superpom/pom.xml then it isn't loading any > of > >> my config files. > >> > >> To be safe, I've even tried adding my .mvn folder in my superpom folder, > >> but that too is ignored. > >> > >> jenkins.log: > >> > >> [superpom] $ /var/jenkins_home/tools/hudson.model.JDK/JDK_7/bin/java > >> -cp /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven33- > >> agent-1.8.1.jar:/var/jenkins_home/tools/hudson.tasks.Maven_ > >> MavenInstallation/Maven_3.3.9/boot/plexus-classworlds-2.5.2. > >> jar:/var/jenkins_home/tools/hudson.tasks.Maven_ > >> MavenInstallation/Maven_3.3.9/conf/logging > >> jenkins.maven3.agent.Maven33Main > >> /var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.3.9 > >> /var/jenkins_home/war/WEB-INF/lib/remoting-3.7.jar > >> /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven33- > >> interceptor-1.8.1.jar > >> /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3- > >> interceptor-commons-1.8.1.jar > >> 38679 > >> <===[JENKINS REMOTING CAPACITY]===>channel started > >> using settings config with name Settings.xml > >> Replacing all maven server entries not found in credentials list is true > >> Executing Maven: -B -f > >> /var/jenkins_home/workspace/JB4(Maven)/superpom/pom.xml > >> -Dmaven.repo.local=/var/jenkins_home/workspace/JB4(Maven)/.repository > >> -s /tmp/settings4167440206098086967.xml clean install > >> [INFO] Scanning for projects... > >> > >> > >> I'm not sure if I am using the .mvn folder incorrectly, if there is > >> something wrong with my Jenkins job configuration. > >> > >> Am I doing this right? Am I missing a step somewhere? > >> > >> Thanks, > >> > >> Eric > >> > > > > > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
