[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_74763 ] Sharmarke Aden commented on MNG-2551: -------------------------------------
Yes, I should have also mentioned that I'm using Continuum as well. This problem occurs when a project depends on another project. If we build the main project, the sub project is built first and during the build of the sub project is when a truncated pom file is installed into the local repository. Now an attempt is made to build the main project, and of course this is when everything comes crashing down because the sub project pom is not a valid/complete XML. I wasn't sure if this is a continuum bug or a artifact, but looking at the continuum code, I saw nothing whacking or bizarre. > pom metadata file gets truncated during install into local repository > --------------------------------------------------------------------- > > Key: MNG-2551 > URL: http://jira.codehaus.org/browse/MNG-2551 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Artifacts > Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 > Reporter: Sharmarke Aden > Attachments: pom.xml, shared-1.9.0.pom > > > When I attempt to install my project artifact to my local repository it seems > that sometimes an incomplete/truncated ".pom" is deployed to my local > repository. It's kind of weird because sometimes it happens and sometimes it > doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and > the truncated pom meta data artifact deployed to my local repository. One > thing I found that's odd is that the size of the truncated pom generated is > consistently 4096 bytes. > p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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
