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

          dtreiber created issue -
          dtreiber made changes -
          Environment Original: Ubuntu 10.04 Server, TomCat 6.0.29 , Hudson 1.394 New: Ubuntu 10.04 Server, TomCat 6.0.29 , Hudson 1.394, maven2.2.1

          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.
          dtreiber made changes -
          Description Original: 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!!!)
          New: 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
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]

          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 made changes -
          Attachment New: testproject-dtreiber25012011.zip [ 20174 ]

          dtreiber added a comment -

          Still failing with Hudson (pardon, Jenkins) 1.397

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

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

              Created:
              Updated: