[MRELEASE-215] mvn release:perform deploys an incomplete pom into repository.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.0-beta-5
• Environment: Windows XP, Java 1.05
• Assignee: Emmanuel Venisse
• Reporter: Marco Antonio Villalobos, Jr.
• Created: 14/Apr/07 14:22
• Updated: 18/May/07 06:59
• Resolved: 18/May/07 06:59

Description

I have had this problem in Maven 2.04, and Maven 2.0.6. My manager also had this problem independently.

When using the mvn release:perform plugin, the pom that it posts into the repository is cut off somewhere in the middle, creating invalid xml, and furthermore, an invalid pom.

Then, when another project that uses this dependency attempts to use this dependency,
it cannot be resolved because the xml in the repository is wrong.

I want to maven through a complete cycle

test compile release.

Attached is the project pom, and and the generated pom version 1.0.5

I would actually private project source if there is a guarantee that it would be kept private and my property.

I consider this a stopper because I want to release my code, but now I cannot because of this bug unless I choose NOT to use Maven. But I love Maven, and I want to continue using it.