cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Braden Shepherdson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CB-4852) Cordova Prepare command removes .svn folders
Date Wed, 25 Sep 2013 18:28:02 GMT

     [ https://issues.apache.org/jira/browse/CB-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Braden Shepherdson resolved CB-4852.
------------------------------------

    Resolution: Won't Fix

The solution to this is to stop version-controlling your platforms/foo directories, or at
least the platforms/.../www directories. They are intended to be build artifacts and get frequently
regenerated.

The problem with overwriting instead is catching what files have been removed; this is not
an easy problem to solve.
                
> Cordova Prepare command removes .svn folders
> --------------------------------------------
>
>                 Key: CB-4852
>                 URL: https://issues.apache.org/jira/browse/CB-4852
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 2.9.0
>            Reporter: Michael
>            Assignee: Braden Shepherdson
>
> Our entire cordova project is under SVN version control. In order for our team to share
development, it must be this way. However, we would like to maintain control over the project
using the CLI for preparing platforms by running "cordova prepare". This command appears to
remove all files in the platform-specific "www" directory and replace with root "www" contents,
however, it should not do this when under source control as the .SVN admin directories are
removed from folders. Instead, I would recommend that a supported operation be performed instead,
such as only overwriting files and possibly removing any that no longer exist in the root
www folder. This would ensure version control systems recognize files have changed, but maintain
their VC bindings. I understand that "hooks" can be created for this, but I truly believe
that is a work-around versus a solution.

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

Mime
View raw message