[
http://jira.codehaus.org/browse/MRELEASE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed MRELEASE-215.
-------------------------------------
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: 2.0-beta-5
I can't reproduce it and don't know how to reproduce it.
If it always occurs, reopen the issue
> mvn release:perform deploys an incomplete pom into repository.
> --------------------------------------------------------------
>
> Key: MRELEASE-215
> URL: http://jira.codehaus.org/browse/MRELEASE-215
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Environment: Windows XP, Java 1.05
> Reporter: Marco Antonio Villalobos, Jr.
> Assignee: Emmanuel Venisse
> Priority: Blocker
> Fix For: 2.0-beta-5
>
> Attachments: kineteque-jsf-1.0.5.pom, pom.xml
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
