On Thu, Nov 21, 2013 at 1:00 PM, Ian Clelland <iclell...@chromium.org>wrote:
> On Thu, Nov 21, 2013 at 2:56 PM, Joe Bowser <bows...@gmail.com> wrote: > > > On Thu, Nov 21, 2013 at 11:37 AM, Ian Clelland <iclell...@chromium.org> > > wrote: > > > > > > Would it make sense to have a build flag for this? "cordova build > > --debug", > > > "cordova build --release"; something like that (bikeshed colours > > welcome). > > > I don't think that config.xml is the place for it; it seems like it > > should > > > be lower than that, but I'm not exactly sure how it should be set. > > > > Considering that we have to add Java code to get this to work, it > > either has to be in the XML, or we're going to have to check the > > AndroidManifest to see if we're in debug mode, like what we already do > > for SSL errors. > > > > If we could set that flag in the manifest from the CLI (as part of prepare, > or as part of build) then that would probably do it. > > > > > > There > > > will probably need to be platform-specific implementations, but it > would > > be > > > good to have a cross-platform way of turning it on and off. > > > > > > > The CLI doesn't have a way to actually release software, so I assume > > that ALL builds created by it are Debug Builds. > > > > True. There should be a thread about that, too :) > What do we mean that the CLI doesn't have a way to release software? Maybe not using a single command, but you certainly can with the workflow.
