Hmmm, I actually thought we were leaving logger in core and not pulling out the console plugin. I at least marked it on jira https://issues.apache.org/jira/browse/CB-3639. We should probably discuss if this is something that we want to pull out into its own plugin. CDVLogger is the reason console.log works for iOS. A case can be made to it in core just so developers get that by default.
On Mon, Jul 1, 2013 at 4:43 PM, Tyler Wilson <twil...@pulse-robotics.com>wrote: > First, I know I should likely not be using 'master', but a named branch > like '2.9.x', but I cannot seem to wrangle git into doing this for me. > > With that out of the way, I just did a git pull on the my locally cloned, > read-only repo. According to the last commit message - "Remove CDVLogger > (moved out to cordova-plugin-console)" - it appears the CDVLogger has been > removed. Which explains the CDVLogger.h/m going away. But I also now get a > message like this for every log: > > 2013-07-01 19:02:07.042 PRUniversal[5873:c07] ERROR: Plugin 'Logger' not > found, or is not a CDVPlugin. Check your plugin mapping in config.xml. > 2013-07-01 19:02:07.042 PRUniversal[5873:c07] -[CDVCommandQueue > executePending] [Line 116] FAILED pluginJSON = [ > "INVALID", > "Logger", > "logLevel", > [ > "LOG", > "onPageChange()" > ] > ] > > Perhaps the commit can contain a more detailed message stating what should > be done instead of the CDVLogger option. It mentions CDVConsole, but I see > not source for this in the CordovaLib project either. > > Help please. > > Thank you, > Tyler
