You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/11/03 22:21:35 UTC

[jira] [Commented] (CB-7881) Android tooling shouldn't lock application directory

    [ https://issues.apache.org/jira/browse/CB-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195111#comment-14195111 ] 

ASF GitHub Bot commented on CB-7881:
------------------------------------

Github user cmarcelk commented on the pull request:

    https://github.com/apache/cordova-android/pull/130#issuecomment-61550705
  
    One of my concerns looking at the changes is that it would leave a new tmp directory laying around on the filesystem everytime one was needed, but looking at the docs for os.tmpdir() I see it just returns the system's default dir for tempfiles. Cool.


> Android tooling shouldn't lock application directory
> ----------------------------------------------------
>
>                 Key: CB-7881
>                 URL: https://issues.apache.org/jira/browse/CB-7881
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>            Reporter: Sergey Grebnov
>            Assignee: Sergey Grebnov
>
> Repro steps:
> 1. From the working directory call “cordova emulate android” (this will start adb + the emulator) 
> 2.Close the emulator
> 3.Now change the directory and try to delete the working directory. (It will complain as being in used).
> This happens due to android tools automatically launch the adb server in the working dir if it is not started yet,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org