[jira] Commented: (MANTRUN-101) last command is skipped and last file is not closed properly if there are subsequent ant calls

["Paul Gier (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MANTRUN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182188#action_182188 ] 

Paul Gier commented on MANTRUN-101:
-----------------------------------

Can you provide more information (ideally a sample project)?  Which file is not being closed properly?  The external build.xml?

> last command is skipped and last file is not closed properly if there are subsequent ant calls
> ----------------------------------------------------------------------------------------------
>
>                 Key: MANTRUN-101
>                 URL: http://jira.codehaus.org/browse/MANTRUN-101
>             Project: Maven 2.x Antrun Plugin
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Stefan Franke
>
> I have a complex project, using pluginmanagement to define stuff and use it later (which also does not work as expected... but that's a separate story).
> It looks like
> grandfather-pom:
> {code}
> ...
>   <pluginmanagement>
> ...
>     <antrun-plugin>
>       <tasks>
>         ...
>         <copy ... />
>         <echo message="done" />
> ...
> {code}
> father-pom:
> {code}
> ...   
>   <pluginmanagement>
> ...
>     <antrun-plugin>
>       <tasks>
>         <ant antfile="... 
> ...
> {code}
> and then in a child a bunch of those antruns is triggered.
> If I run it at the child, everything is ok.
> If I run it from any parent up to grandfather, the last message of the inlined ant task vanishes and the last file is not closed properly (ending up with a zero length 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