ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Commented: (IVY-605) XmlReportOutputter not safe
Date Thu, 28 Feb 2008 18:07:51 GMT


Xavier Hanin commented on IVY-605:

There's another workaround in latest ivy version: use a separate resolution cache for concurrent
resolve. I don't think we need to support the use case of concurrent resolve execution with
these two workarounds. Hence I think we should just double check the documentation clearly
states that we don't support this, and then mark this bug as resolved wontfix.

> XmlReportOutputter not safe
> ---------------------------
>                 Key: IVY-605
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jean-Baptiste Quenot
>             Fix For: 2.0
> When issuing several "resolve" task in parallel on several projects having the *same*
Ivy file, it may happen that the generated XML reports in ivy cache are overwritten.  And
thus at a given moment in time, this file may appear empty, as FileOutputStream overwrites
the destination directly.  When using the "report" task (also in parallel), this leads to
the following error:
> {noformat}
> [ivy:report] Transforming into /path/to/myproject/target/ivy-reports
> [ivy:report] Processing /path/to/ivy-cache/myproject-compile.xml to /path/to/myproject/target/ivy-reports/myproject-compile.html
> [ivy:report] Loading stylesheet /path/to/ivy-cache/ivy-report.xsl
> [ivy:report] Processing /path/to/ivy-cache/myproject-default.xml to /path/to/myproject/target/ivy-reports/myproject-default.html
> [ivy:report] : Error! Premature end of file.
> build.xml:19: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: Premature end of file.
> Total time: 33 seconds
> [ivy:report] : Error!
Premature end of file.
> [ivy:report] Failed to process null
> {noformat}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message