cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-4191) `cordova serve` not reflecting changes to files; unusable for development
Date Fri, 12 Jul 2013 18:55:48 GMT

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

Filip Maj commented on CB-4191:
-------------------------------

It looks like [~brentlintner] fixed the windows 7 ripple issue (thanks dude!)

I will re-enable Ripple and push 2.9.5 shortly. 
                
> `cordova serve` not reflecting changes to files; unusable for development
> -------------------------------------------------------------------------
>
>                 Key: CB-4191
>                 URL: https://issues.apache.org/jira/browse/CB-4191
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Sam Breed
>            Assignee: Filip Maj
>
> I ran into this after upgrading from 2.7 to 2.9, but the change appears to be introduced
in 2.8. `cordova serve` isn't reflecting changes in the files that it's serving, which makes
it useless as a development server.
> Here's a screenshot of the behavior:
> !http://cl.ly/image/3p182c0Z451l/i|width=600!
> I brought this up in IRC when I first encountered it and was told that `cordova serve`
was on its way to being deprecated in 3.0, and I should use `cordova ripple` instead.
> Turns out that ripple was **removed** to address [CB-4058] (and in a minor version release!)
leaving cordova with no server that you can run without having to restart it every. time.
you. change. a. file. It looks like the underlying issue in CB-4058 has been addressed upstream
in ripple, so hopefully it can be put back in and released quickly.
> BUT the caching issue with serve still exists and is preventing me from upgrading.

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