[
http://jira.codehaus.org/browse/MOJO-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203995#action_203995
]
Igor Jacy Lino Campista commented on MOJO-1481:
-----------------------------------------------
its not a workaround, because thats not what I can do in the continous
integration.
After running the startupCmd.bat, I don't use the window that appears but still
the same command line where I executed startupCmd.bat
The 1st sample.zip contains only failure. (after means using the pop console
window, where it also fails)
The 2nd sample_after_success.zip is when it worked.
I notice its still a bit of random, and looks like is not the only file that
can get locked.
> pdf script fails with locked file (using dita-maven-plugin)
> -----------------------------------------------------------
>
> Key: MOJO-1481
> URL: http://jira.codehaus.org/browse/MOJO-1481
> Project: Mojo
> Issue Type: Bug
> Components: dita
> Reporter: Igor Jacy Lino Campista
> Attachments: sample.zip, sample_after_success.zip
>
>
> Hi,
> I have been generating PDFs as part of the a continous integration server
> using the DITA OT 1.5 M22 and the dita-maven plugin 1.0beta1.
> After using the latest DITA OT 1.5 final release, the script fails at the
> end due to a clean up that cannot be completed.
> The error log is:
> <delete.fo2pdf.topic.fo:
> <
> <topic2pdf2:
> <
> <dita2pdf2:
> <
> <clean-temp:
> <
> <BUILD FAILED
> <C:\calypso-tools\calypso_trunk\documentation\lib\target\DITA-OT1.5\build.x
> ml:66: The following error occurred while executing this line:
> <C:\calypso-tools\calypso_trunk\documentation\lib\target\DITA-OT1.5\build_p
> reprocess.xml:15: Unable to delete file
> C:\calypso-tools\calypso_trunk\documentation\calypso-developer-environment-
> installation-guide\target\dita\temp\Calypso-developer-guide_MERGED.xml
> Somehow that temporal merged xml file is locked by something during the
> script processing.
> I modified the script to not fail (failonerror="false") on that delete
> task. It obviously works, and the script finishes. Afterwards, looking at
> the temp directory, only the file is found. This indicates something has a
> lock on that file.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
