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

Tommy-Carlos Williams commented on CB-2820:
-------------------------------------------

More fun times.

`cordova prepare ...` is fine without the .DS_Store issue.

Running `cordova prepare ...` then `cordova compile ...` is also fine.

However, running `cordova emulate ...` then clobbers my ./platforms/.../www 
folder.   

????

Should emulate be changing anything? Or should it just be doing the same as say 
./cordova/run || ./cordova/emulate etc?

So... actually... *don't* close this after all.

                
> Plugins added via the CLI are clobbered during prepare
> ------------------------------------------------------
>
>                 Key: CB-2820
>                 URL: https://issues.apache.org/jira/browse/CB-2820
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 2.6.0
>            Reporter: Tommy-Carlos Williams
>            Assignee: Filip Maj
>              Labels: plugin
>
> Latest CLI (2.6.0) - add a plugin using `cordova add plugin /path/to/plugin` 
> and the src is copied into the correct locations in the ./platforms/* folders 
> but the js from the plugin is not copied into the "main" ./www folder.
> Therefore, when you run `cordova build <platform>` the prepare stage copies 
> over the ./platforms/.../www folder with the main app one in ./www 
> effectively removing the plugin's js file from the platform's www folder and 
> rendering the plugin broken.
> It seems like it is in a halfway state between the "old" way of installing 
> the plugin's js into ./www on the first `cordova plugin add ...` and the 
> "new" way of installing the plugin into ./platforms/* during prepare. 

--
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

Reply via email to