Return-Path: Delivered-To: apmail-ant-notifications-archive@locus.apache.org Received: (qmail 43552 invoked from network); 28 Feb 2008 18:08:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Feb 2008 18:08:49 -0000 Received: (qmail 54622 invoked by uid 500); 28 Feb 2008 18:08:44 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 54605 invoked by uid 500); 28 Feb 2008 18:08:44 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 54596 invoked by uid 99); 28 Feb 2008 18:08:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2008 10:08:44 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2008 18:08:06 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2A29B234C00F for ; Thu, 28 Feb 2008 10:07:51 -0800 (PST) Message-ID: <96813177.1204222071156.JavaMail.jira@brutus> Date: Thu, 28 Feb 2008 10:07:51 -0800 (PST) From: "Xavier Hanin (JIRA)" To: notifications@ant.apache.org Subject: [jira] Commented: (IVY-605) XmlReportOutputter not safe MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVY-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573383#action_12573383 ] 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: https://issues.apache.org/jira/browse/IVY-605 > 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 FAILED > build.xml:19: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Premature end of file. > Total time: 33 seconds > [ivy:report] : Error! com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: 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.