Could also inject a post-prepare hook to get in there. I think it'd be even better though, to just figure out how to not need to do the "hack a little bit" part.
On Mon, Aug 12, 2013 at 5:06 PM, Filip Maj <[email protected]> wrote: > > >Generally true. There are a few bits in the device deployment part that > >need code that is not part of cli and probably don't make sense to be > >there. There are some bits that probably should be handled by extensions > >to > >cli since there are other reasonable workflows that could use them. > > > >For example - Currently cli does not offer a build-deploy only option, > >which is a problem. For the current method to work, we need to prepare - > >hack a little - build & deploy. All of the cli options do a prepare first. > >So for my first tests I have called the lib scripts directly for that too. > >I think adding deploy-only to cli makes sense. > > We don't offer a deploy-only api through cordova-cli, but we do offer a > `compile` command: this is a build without a prepare. I am not sure > whether it is worth exposing this stuff in cordova-cli, or if keeping it > to the project/cordova/lib scripts is sufficient. I think at this point, > keeping them under lib/ is good enough. If people really need it, they can > call into the lib/ scripts by going through ~userdir/.cordova/lib/android > manually and invoking scripts that way. > > > > >I am less sure that deploying to multiple devices has a target audience > >other than automated testing... > > In general I've always been surprised by what users will do if you provide > them with the capabilities.. :) > >
