Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-268

Invalid POM for clover 2.3.1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 2.3.2
    • 2.3.1
    • Ant Tasks
    • None

    • maven 2.0.9, java 1.5.0_13

      There is an empty 'build.resources.resource.directory' entry in the POM:
      ...
      <resource>
      <targetPath>jars</targetPath>
      <directory></directory> <Unable to render embedded object: File (-- empty) not found.!! -->
      <includes>
      <include>clover-2.3.1.jar</include>
      </includes>
      </resource>
      </resources>
      ...

      Maven complains about it:

      [WARNING] POM for 'com.cenqua.clover:clover:pom:2.3.1:provided' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project com.cenqua.clover:clover at Artifact [com.cenqua.clover:clover:pom:2.3.1:provided]
      [DEBUG] Reason: Failed to validate POM for project com.cenqua.clover:clover at Artifact [com.cenqua.clover:clover:pom:2.3.1:provided]
      [DEBUG]
      Validation Errors:
      [DEBUG] 'build.resources.resource.directory' is missing.

      Maybe a '.' value for the directory will work?

            [CLOV-268] Invalid POM for clover 2.3.1

            Nick added a comment -

            assigning to the 2.3.1 release

            Nick added a comment - assigning to the 2.3.1 release

            Nick added a comment -

            Hi Marcel,

            This was fixed overnight. I can now install the clover-maven2-plugin from maven central:

            [INFO] Preparing clover2:instrument
Downloading: http://repo1.maven.org/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom
756b downloaded
Downloading: http://repo1.maven.org/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.jar
8110K downloaded
[INFO] [clover2:instrumentInternal]

            Please let me know how you go.
            Cheers,
            Nick

            Nick added a comment - Hi Marcel, This was fixed overnight. I can now install the clover-maven2-plugin from maven central: [INFO] Preparing clover2:instrument Downloading: http: //repo1.maven.org/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom 756b downloaded Downloading: http: //repo1.maven.org/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.jar 8110K downloaded [INFO] [clover2:instrumentInternal] Please let me know how you go. Cheers, Nick

            James Dumay added a comment -

            Ive opened an issue with the Maven project to get this sorted out

            See
            http://jira.codehaus.org/browse/MAVENUPLOAD-2015

            Thanks
            James

            James Dumay added a comment - Ive opened an issue with the Maven project to get this sorted out See http://jira.codehaus.org/browse/MAVENUPLOAD-2015 Thanks James

            Nick added a comment -

            Hi James,

            As discussed, this is a related to the maven1 pom in maven's maven2 repo.

            Cheers,
            Nick

            Nick added a comment - Hi James, As discussed, this is a related to the maven1 pom in maven's maven2 repo. Cheers, Nick

            Nick added a comment -

            Hi Marcel!

            Thank you very much for pointing this out. I was not aware that we had 2 different poms on two different repositories for the same artifact. This is obviously not ideal and is something we are trying to rectify at the moment.

            The current pom deployed at http://mirrors.ibiblio.org/pub/mirrors/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom was intended for the Maven1 repo, not for Maven2. I am not sure why the modelVersion is set to 4.0.0, the project.xml which we supplied has modelVersion 3.

            Hopefully this will be fixed shortly.

            Cheers,
            Nick.

            Nick added a comment - Hi Marcel! Thank you very much for pointing this out. I was not aware that we had 2 different poms on two different repositories for the same artifact. This is obviously not ideal and is something we are trying to rectify at the moment. The current pom deployed at http://mirrors.ibiblio.org/pub/mirrors/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom was intended for the Maven1 repo, not for Maven2. I am not sure why the modelVersion is set to 4.0.0, the project.xml which we supplied has modelVersion 3. Hopefully this will be fixed shortly. Cheers, Nick.

            Marcel May added a comment -

            Hi Nick!

            Ah, I see there are different POMs on different repos. By default, our mvn proxy queries ibiblio/central first before trying other repos like the Atlassian one.

            Broken POM:
            http://mirrors.ibiblio.org/pub/mirrors/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom

            Good POM:
            http://repository.atlassian.com/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom

            Hm, I wonder if the Ibiblio POM could get replaced since it is invalid. Usually, there's a policy of not modifying published artifacts. Obviously, a broken POM getting fixed can not break a build. Though once fetched it would not get replaced.

            I guess the best thing would be to wait for 2.3.2 and close this issue
            Sorry for the trouble.

            Cheers,
            Marcel

            Marcel May added a comment - Hi Nick! Ah, I see there are different POMs on different repos. By default, our mvn proxy queries ibiblio/central first before trying other repos like the Atlassian one. Broken POM: http://mirrors.ibiblio.org/pub/mirrors/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom Good POM: http://repository.atlassian.com/maven2/com/cenqua/clover/clover/2.3.1/clover-2.3.1.pom Hm, I wonder if the Ibiblio POM could get replaced since it is invalid. Usually, there's a policy of not modifying published artifacts. Obviously, a broken POM getting fixed can not break a build. Though once fetched it would not get replaced. I guess the best thing would be to wait for 2.3.2 and close this issue Sorry for the trouble. Cheers, Marcel

            Nick added a comment -

            Hi Marcel,

            Could you please provide me with a link to the pom you are referring to?

            Cheers,
            Nick

            Nick added a comment - Hi Marcel, Could you please provide me with a link to the pom you are referring to? Cheers, Nick

              npellow Nick
              39a0ddf54942 Marcel May
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: