You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Matthias Brandt (JIRA)" <ji...@apache.org> on 2011/08/19 11:08:27 UTC

[jira] [Created] (BUILDR-608) rm_rf doesn't work with broken symbolic link

rm_rf doesn't work with broken symbolic link
--------------------------------------------

                 Key: BUILDR-608
                 URL: https://issues.apache.org/jira/browse/BUILDR-608
             Project: Buildr
          Issue Type: Bug
          Components: Core features, JRuby
         Environment: Buildr 1.6.3, Kubuntu 11.04, Java 1.6.0_26, rubygems 1.5.1
            Reporter: Matthias Brandt


Steps to reproduce:
1) ln -s /path/which/does/not/exist link
2) put "rm_rf link" in your clean target
3) run "buildr clean" on JRuby

In MRI ruby, everything works fine...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BUILDR-608) rm_rf doesn't work with broken symbolic link

Posted by "Peter Donald (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald updated BUILDR-608:
--------------------------------

    Fix Version/s: 1.5
    
> rm_rf doesn't work with broken symbolic link
> --------------------------------------------
>
>                 Key: BUILDR-608
>                 URL: https://issues.apache.org/jira/browse/BUILDR-608
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features, JRuby
>         Environment: Buildr 1.6.3, Kubuntu 11.04, Java 1.6.0_26, rubygems 1.5.1
>            Reporter: Matthias Brandt
>              Labels: ln, rm_rf
>             Fix For: 1.5
>
>
> Steps to reproduce:
> 1) ln -s /path/which/does/not/exist link
> 2) put "rm_rf link" in your clean target
> 3) run "buildr clean" on JRuby
> In MRI ruby, everything works fine...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira