couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garren Smith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1860) Dev server bug with addons
Date Tue, 30 Jul 2013 07:23:53 GMT

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

Garren Smith commented on COUCHDB-1860:
---------------------------------------

We actually need to create a dependancy list in settings.json and settings.json.default. Then
union that with settins.json.default and settings.json module list. There is a definite use
case of having a module that another module might depend on while the first module should
not be loaded up. Another reasons is ExampleAuth is not used at the moment but is an example
of how to use Auth with Fauxton. If we had to just do a union on the loaded modules we would
end up deleting that module.
                
> Dev server bug with addons
> --------------------------
>
>                 Key: COUCHDB-1860
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1860
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Fauxton
>            Reporter: Sue Lockwood
>
> When you set addons in your settings.json file and run the dev server,
> the grunt task does not clean out the addon's folder of any old addons that may have
been loaded previously.
> There is also a bug with the watch files not watching edits in the source folders and
then moving the edits to the fauxton addon folder. 

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