Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8544

Hudson wont resolve parameters in VersionTag

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • maven-plugin
    • None
    • Ubuntu 10.04 Server, TomCat 6.0.29 , Hudson 1.394, maven2.2.1

      ERROR: POMs konnten nicht geparst werden
      org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      [FATAL] Non-resolvable parent POM: Could not find artifact de.inter.hus.kosmo:AngebotWebHUSAssembly:pom:${angebotwebHusVersion} in prod (http://xxxx/nexus/content/repositories/prod) and 'parent.relativePath' points at wrong local POM @ line 12, column 10

      at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
      at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
      at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
      at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
      at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1253)
      at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1159)
      at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:991)
      at hudson.FilePath.act(FilePath.java:756)
      at hudson.FilePath.act(FilePath.java:738)
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:698)
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:531)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
      at hudson.model.Run.run(Run.java:1362)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:145)
      Finished: FAILURE

      --> Worked without problems under Hudson 1.391.
      Problem since 1.392
      Seems Hudson or Maven wont resolve given parameters!
      Excerpt from pom:

      <properties>
      <angebotwebHusVersion>1.2.0-SNAPSHOT</angebotwebHusVersion>
      </properties>
      <groupId>xxx.hus.kosmo</groupId>
      <artifactId>AngebotWebHUSAssembly</artifactId>
      <version>${angebotwebHusVersion}</version>
      <packaging>pom</packaging>
      <name>AngebotWebHUSAssembly</name>

      --> Rolled back to 1.393 (still failure)
      --> Rolled back to 1.392 (still failure)
      --> Rolled back to 1.391 (works!!!)
      Update:
      --> Version 1.395 Also fails!! (also with Tomcat7.0.6)
      Changed Priority to: BLOCKER

          [JENKINS-8544] Hudson wont resolve parameters in VersionTag

          skybeam added a comment -

          I can confirm this issue. It happens to my projects as well.

          skybeam added a comment - I can confirm this issue. It happens to my projects as well.

          Olivier Lamy added a comment -

          do you have any sample project for this ?
          BTW with 1.395 in the advanced option for maven build you change the maven pom validation level.
          I recommend you use minimal or MAVEN_2_0
          Does your project declare a parent pom ?

          Olivier Lamy added a comment - do you have any sample project for this ? BTW with 1.395 in the advanced option for maven build you change the maven pom validation level. I recommend you use minimal or MAVEN_2_0 Does your project declare a parent pom ?

          SkyBeam added a comment -

          I don't have a sample project right now. But yes, the projects use a parent.

          I think any simple project which uses a property within the version tag should trigger the error. I will verify the maven level specification in job properties as well.

          I plan to perform some tests tomorrow.

          SkyBeam added a comment - I don't have a sample project right now. But yes, the projects use a parent. I think any simple project which uses a property within the version tag should trigger the error. I will verify the maven level specification in job properties as well. I plan to perform some tests tomorrow.

          dtreiber added a comment - - edited

          @olamy
          do you have any sample project for this ? --> attached
          BTW with 1.395 in the advanced option for maven build you change the maven pom validation level.
          I recommend you use minimal or MAVEN_2_0 --> already was minimal
          Does your project declare a parent pom ? --> yes but it doesnt matter with or without

          I did some tests building a simple project and received additional problems!!

          i will attach the sample project to this issue

          dtreiber added a comment - - edited @olamy do you have any sample project for this ? --> attached BTW with 1.395 in the advanced option for maven build you change the maven pom validation level. I recommend you use minimal or MAVEN_2_0 --> already was minimal Does your project declare a parent pom ? --> yes but it doesnt matter with or without I did some tests building a simple project and received additional problems!! i will attach the sample project to this issue

          dtreiber added a comment - - edited

          after some testing i finally received this:
          startproject is testproject1 (files are attached)

          hudson throws:

          2011 9:43:40 AM UTC" testproject1 testproject2
          $ computing changelog
          Found mavenVersion 2.2.1 from file jar:file:/opt/maven2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
          Parsing POMs
          ERROR: Processing failed due to a bug in the code. Please report this to hudson-users@googlegroups.com
          java.lang.NullPointerException
          at hudson.FilePath.isAbsolute(FilePath.java:224)
          at hudson.FilePath.<init>(FilePath.java:212)
          at hudson.FilePath.child(FilePath.java:894)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:554)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420)
          at hudson.model.Run.run(Run.java:1362)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:145)
          project=hudson.maven.MavenModuleSet@2d0f1d[testfailureproject]
          project.getModules()=[hudson.maven.MavenModule@bb4521[testfailureproject/de.test:testproject1][testfailureproject/de.test:testproject1][relativePath:testproject1], hudson.maven.MavenModule@b79ed4[testfailureproject/de.test:testproject2][testfailureproject/de.test:testproject2][relativePath:null]]
          project.getRootModule()=hudson.maven.MavenModule@bb4521[testfailureproject/de.test:testproject1][testfailureproject/de.test:testproject1][relativePath:testproject1]
          FATAL: null
          java.lang.NullPointerException
          at hudson.FilePath.isAbsolute(FilePath.java:224)
          at hudson.FilePath.<init>(FilePath.java:212)
          at hudson.FilePath.child(FilePath.java:894)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:554)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420)
          at hudson.model.Run.run(Run.java:1362)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:145)

          dtreiber added a comment - - edited after some testing i finally received this: startproject is testproject1 (files are attached) hudson throws: 2011 9:43:40 AM UTC" testproject1 testproject2 $ computing changelog Found mavenVersion 2.2.1 from file jar: file:/opt/maven2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties Parsing POMs ERROR: Processing failed due to a bug in the code. Please report this to hudson-users@googlegroups.com java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:224) at hudson.FilePath.<init>(FilePath.java:212) at hudson.FilePath.child(FilePath.java:894) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:554) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420) at hudson.model.Run.run(Run.java:1362) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) project=hudson.maven.MavenModuleSet@2d0f1d [testfailureproject] project.getModules()=[hudson.maven.MavenModule@bb4521 [testfailureproject/de.test:testproject1] [testfailureproject/de.test:testproject1] [relativePath:testproject1] , hudson.maven.MavenModule@b79ed4 [testfailureproject/de.test:testproject2] [testfailureproject/de.test:testproject2] [relativePath:null] ] project.getRootModule()=hudson.maven.MavenModule@bb4521 [testfailureproject/de.test:testproject1] [testfailureproject/de.test:testproject1] [relativePath:testproject1] FATAL: null java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:224) at hudson.FilePath.<init>(FilePath.java:212) at hudson.FilePath.child(FilePath.java:894) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:554) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420) at hudson.model.Run.run(Run.java:1362) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)

          dtreiber added a comment -

          Still failing with Hudson (pardon, Jenkins) 1.397

          dtreiber added a comment - Still failing with Hudson (pardon, Jenkins) 1.397

          evernat added a comment -

          dtreiber: can you confirm that this issue is or is not a duplicate of the JENKINS-8602 issue, which is supposed to be fixed in Jenkins 1.403 ?

          evernat added a comment - dtreiber: can you confirm that this issue is or is not a duplicate of the JENKINS-8602 issue, which is supposed to be fixed in Jenkins 1.403 ?

          dtreiber added a comment -

          I can confirm that this is not the same issue, as it still fails with Jenkins 1.409:
          (The problem seems to be the properties resolution, which is defined in a parent POM, and used by any project which depends on that parent and has this property set as version.
          Commandline maven works with this setting.)

          Gestartet durch Benutzer treiber [workspace] $ cvs -Q -z3 -d :pserver:xxx@dsnsv260.inter.de:/usr/local/inter/cvs/cvsrepo/vpp co -P -D "Tuesday, April 26, 2011 9:54:49 AM UTC" PvsAdminWeb PvsAdminWebEAR PvsAdminServer $ computing changelog ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro Found mavenVersion 2.2.1 from file jar:file:/opt/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties Parsing POMs
          downloaded artifact http://xxx/nexus/content/repositories/prod//de/inter/pvs/PVSPOM/1.0.0/PVSPOM-1.0.0.pom failed to transfer Unable to locate resource in repository failed to transfer Unable to locate resource in repository
          failed to transfer Unable to locate resource in repository ERROR: POMs konnten nicht geparst werden org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact de.inter.pvs.admin:PvsAdminServer:pom:${pvs.admin.build.version} in prod (http://xxx/nexus/content/repositories/prod) and 'parent.relativePath' points at wrong local POM @ line 16, column 11 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321) at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1381) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1288) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1110) at hudson.FilePath.act(FilePath.java:756) at hudson.FilePath.act(FilePath.java:738) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423) at hudson.model.Run.run(Run.java:1362) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro [workspace] $ /bin/sh -xe /opt/apache-tomcat-7.0.12/temp/hudson5742296311114778951.sh + rm -r /usr/local/inter/jenkins/jobs/PvsAdminServer_Test/workspace Finished: FAILURE

          dtreiber added a comment - I can confirm that this is not the same issue, as it still fails with Jenkins 1.409: (The problem seems to be the properties resolution, which is defined in a parent POM, and used by any project which depends on that parent and has this property set as version. Commandline maven works with this setting.) Gestartet durch Benutzer treiber [workspace] $ cvs -Q -z3 -d :pserver:xxx@dsnsv260.inter.de:/usr/local/inter/cvs/cvsrepo/vpp co -P -D "Tuesday, April 26, 2011 9:54:49 AM UTC" PvsAdminWeb PvsAdminWebEAR PvsAdminServer $ computing changelog ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro Found mavenVersion 2.2.1 from file jar: file:/opt/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties Parsing POMs downloaded artifact http://xxx/nexus/content/repositories/prod//de/inter/pvs/PVSPOM/1.0.0/PVSPOM-1.0.0.pom failed to transfer Unable to locate resource in repository failed to transfer Unable to locate resource in repository failed to transfer Unable to locate resource in repository ERROR: POMs konnten nicht geparst werden org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact de.inter.pvs.admin:PvsAdminServer:pom:${pvs.admin.build.version} in prod ( http://xxx/nexus/content/repositories/prod ) and 'parent.relativePath' points at wrong local POM @ line 16, column 11 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321) at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1381) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1288) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1110) at hudson.FilePath.act(FilePath.java:756) at hudson.FilePath.act(FilePath.java:738) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423) at hudson.model.Run.run(Run.java:1362) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro [workspace] $ /bin/sh -xe /opt/apache-tomcat-7.0.12/temp/hudson5742296311114778951.sh + rm -r /usr/local/inter/jenkins/jobs/PvsAdminServer_Test/workspace Finished: FAILURE

          bnidave added a comment -

          I am having the same problem with 1.409
          This error is preventing me from upgrading from 1.386
          Also, I can run perfectly fine from the command line as well.

          ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro
          Found mavenVersion 2.2.1 from file jar:file:/workspace/hudson/tools/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
          ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro
          .
          .
          .
          Deleting /workspace/hudson/jobs/project/workspace/.repository/xxx/yyyyy/master-pom/1.0-SNAPSHOT/resolver-status.properties
          Deleting /workspace/hudson/jobs/core-components/workspace/.repository/xxx/yyyyy/master-pom/1.0-SNAPSHOT/master-pom-1.0-SNAPSHOT.pom.lastUpdated
          Parsing POMs
          failed to transfer Unable to locate resource in repository
          failed to transfer Unable to locate resource in repository
          ERROR: Failed to parse POMs
          org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
          [WARNING] 'version' contains an expression but should be a constant. @ line 13, column 12
          [FATAL] Non-resolvable parent POM: Could not find artifact xxx.yyyyy:master-pom:pom:1.0-SNAPSHOT in nexus (http://xxx/nexus/content/groups/public) and 'parent.relativePath' points at wrong local POM @ line 4, column 11

          at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339)
          at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
          at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
          at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
          at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1381)
          at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1384)
          at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1288)
          at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1110)
          at hudson.FilePath.act(FilePath.java:756)
          at hudson.FilePath.act(FilePath.java:738)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423)
          at hudson.model.Run.run(Run.java:1362)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:145)
          ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro

          bnidave added a comment - I am having the same problem with 1.409 This error is preventing me from upgrading from 1.386 Also, I can run perfectly fine from the command line as well. ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro Found mavenVersion 2.2.1 from file jar: file:/workspace/hudson/tools/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro . . . Deleting /workspace/hudson/jobs/project/workspace/.repository/xxx/yyyyy/master-pom/1.0-SNAPSHOT/resolver-status.properties Deleting /workspace/hudson/jobs/core-components/workspace/.repository/xxx/yyyyy/master-pom/1.0-SNAPSHOT/master-pom-1.0-SNAPSHOT.pom.lastUpdated Parsing POMs failed to transfer Unable to locate resource in repository failed to transfer Unable to locate resource in repository ERROR: Failed to parse POMs org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [WARNING] 'version' contains an expression but should be a constant. @ line 13, column 12 [FATAL] Non-resolvable parent POM: Could not find artifact xxx.yyyyy:master-pom:pom:1.0-SNAPSHOT in nexus ( http://xxx/nexus/content/groups/public ) and 'parent.relativePath' points at wrong local POM @ line 4, column 11 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321) at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1381) at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1384) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1288) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1110) at hudson.FilePath.act(FilePath.java:756) at hudson.FilePath.act(FilePath.java:738) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423) at hudson.model.Run.run(Run.java:1362) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro

            dtreiber dtreiber
            dtreiber dtreiber
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: