[
http://jira.codehaus.org/browse/MNG-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2909:
-------------------------------
Description:
I was getting build fails because of this:
Caused by: java.io.EOFException: input contained no data
at
org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2979)
at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3022)
at
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1407)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
at
org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:863)
at
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata(AbstractRepositoryMetadata.java:98)
at
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository(AbstractRepositoryMetadata.java:68)
... 21 more
It happened after cancelling a previous build, presumably mid-update of the
metadata.
Probably 2 things to do here:
a) This error should be handled when reading back the metadata to merge, and
treated as a non-existent file instead of an error.
b) use an atomic rename instead of overwriting an existing file to prevent
dataloss in the even of a cancelled build
was:
I was getting build fails because of this:
Caused by: java.io.EOFException: input contained no data
at
org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2979)
at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3022)
at
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1407)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
at
org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:863)
at
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata(AbstractRepositoryMetadata.java:98)
at
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository(AbstractRepositoryMetadata.java:68)
... 21 more
It happened after cancelling a previous build, presumably mid-update of the
metadata.
Probably 2 things to do here:
a) This error should be handled when reading back the metadata to merge, and
treated as a non-existent file instead of an error.
b) use an atomic rename instead of overwriting an existing file to prevent
dataloss in the even of a cancelled build
We need to make a little utility for writing out files atomically and use it
everywhere. Or build this capability into the writers generated by modello.
> zero length files can be created for metadata
> ---------------------------------------------
>
> Key: MNG-2909
> URL: http://jira.codehaus.org/browse/MNG-2909
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Brett Porter
> Fix For: 2.0.7
>
>
> I was getting build fails because of this:
> Caused by: java.io.EOFException: input contained no data
> at
> org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2979)
> at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3022)
> at
> org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1407)
> at
> org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392)
> at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
> at
> org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:863)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata(AbstractRepositoryMetadata.java:98)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository(AbstractRepositoryMetadata.java:68)
> ... 21 more
> It happened after cancelling a previous build, presumably mid-update of the
> metadata.
> Probably 2 things to do here:
> a) This error should be handled when reading back the metadata to merge, and
> treated as a non-existent file instead of an error.
> b) use an atomic rename instead of overwriting an existing file to prevent
> dataloss in the even of a cancelled build
--
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
