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

POMs parsing fails in m2 projects which has a wrong inheritence (m3 constraint)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • maven-plugin
    • None

      It occurs with Hudson ver. 1.393-SNAPSHOT (private-01/01/2011 21:34-olamy) but probably also with latest 1.392
      The test case is simple.
      A project with a parent like this :

      <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
        <modelVersion>4.0.0</modelVersion>
        <groupId>org.hudson-ci.testcase</groupId>
        <artifactId>wrong-inheritence-parent</artifactId>
        <version>1.0-SNAPSHOT</version>
        <packaging>pom</packaging>
        <modules>
                <module>subdir/mod1</module>
        </modules>
</project>

      And in the module subdir/mod1

      <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
        <modelVersion>4.0.0</modelVersion>
        <parent>
                <groupId>org.hudson-ci.testcase</groupId>
                <artifactId>wrong-inheritence-parent</artifactId>
                <version>1.0-SNAPSHOT</version>
        </parent>
        <artifactId>wrong-inheritence-module</artifactId>
        <packaging>jar</packaging>
</project>

      Not that there is no module in subdir and mod1 doesn't say where to find its parent with a relative path.
      Such a build passes with M2 and fails with m3 with an error like :

      [ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.hudson-ci.testcase:wrong-inheritence-module:1.0-SNAPSHOT (/Users/arnaud/Code/Hudson/incorrect-inheritence-testcase/subdir/mod1/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not find artifact org.hudson-ci.testcase:wrong-inheritence-parent:pom:1.0-SNAPSHOT in exo-fr-mirror (http://repository.exoplatform.org/public) and 'parent.relativePath' points at wrong local POM @ line 4, column 17 -> [Help 2]

      The issue with using m3 to parse m2 projects is that some builds that passed previously (because it was allowed by m2) doesn't work anymore.
      I attach a testcase

        1. incorrect-inheritence-testcase.zip
          2 kB

            olamy Olivier Lamy
            aheritier Arnaud Héritier
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: