[
http://jira.codehaus.org/browse/MOJO-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203066#action_203066
]
Brian Atkinson commented on MOJO-1447:
--------------------------------------
We may want to explicitly clean up the output file rather then rely on the
"deleteOnExit" method. If this code is run in the context of a m2eclipse
build, it may be possible that the eclipse jvm will not be shut down for quite
some time (I usually just leave eclipse up weeks at a time). Lets just
explicitly delete the file after we copy it and if that fails, register it to
be deleted on jvm shutdown.
> Transforming file in-place fails
> --------------------------------
>
> Key: MOJO-1447
> URL: http://jira.codehaus.org/browse/MOJO-1447
> Project: Mojo
> Issue Type: Improvement
> Components: xml
> Reporter: luke w patterson
> Assignee: Jochen Wiedmann
> Priority: Minor
> Attachments: MOJO-1447.patch, stack_trace.txt
>
>
> Currently, if my output path is the same as the input path (i.e. I want to
> transform a file where it sits, without copying it anywhere), I get an
> exception and the file is set to empty.
> It would be nice if I could transform a file in-place. My use-case is a
> little weird, I want to tweak the Eclipse .classpath file on the project root
> without copying it anywhere.
> Stacktrace is attached. Sorry I didn't create unit test and patch, I was
> hoping this might be a simple fix for someone who is already knowledgeable
> with the code.
> Thanks,
> Luke
--
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
