[#CLOV-268] Invalid POM for clover 2.3.1

Clover

Invalid POM for clover 2.3.1

Created: 26/May/08 06:11 AM Updated: 30/Jun/08 07:47 PM

Component/s:

Ant Tasks

Affects Version/s:

2.3.1

Fix Version/s:

2.3.2

Time Tracking:

Not Specified

Environment:

maven 2.0.9, java 1.5.0_13

Participants:	James Dumay [Atlassian], Marcel May and Nick Pellow [Atlassian]
Since last comment:	22 weeks ago
Resolution Date:	30/Jun/08 07:47 PM
Labels:

Description

« Hide

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?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Nick Pellow [Atlassian] added a comment - 26/May/08 06:52 PM

Hi Marcel,

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

Cheers,
Nick

[ Permlink | « Hide ]

Marcel May added a comment - 27/May/08 04:28 AM

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

[ Permlink | « Hide ]

Nick Pellow [Atlassian] added a comment - 27/May/08 07:27 PM

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.

[ Permlink | « Hide ]

Nick Pellow [Atlassian] added a comment - 05/Jun/08 01:52 AM

Hi James,

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

Cheers,
Nick

[ Permlink | « Hide ]

James Dumay [Atlassian] added a comment - 05/Jun/08 02:31 AM

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

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

Thanks
James

[ Permlink | « Hide ]

Nick Pellow [Atlassian] added a comment - 05/Jun/08 09:22 PM

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

[ Permlink | « Hide ]

Nick Pellow [Atlassian] added a comment - 30/Jun/08 07:47 PM

assigning to the 2.3.1 release