What should the reference to the plugman doc be? I can follow the WP upgrade docs, but that part is not there yet I don't think. https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=blob;f=docs/en/edge/guide/platforms/wp8/upgrading.md;h=6d8f37ea10a424f7a72b2f32051ff341790710db;hb=HEAD
On Wed, Jul 17, 2013 at 1:06 PM, Michael Sierra <msie...@adobe.com> wrote: > I committed a change to the CLI doc that details plugin add/rm/ls based on > this doc. The plugman interface should be doc'ed separately to avoid > confusion. Am editing the plugman doc a bit & will figure out where to > place it, but I'd like to confirm the overall use case. I see it as: you > want to upgrade to 3.0, which requires you to add plugins for device APIs, > but for whatever reason you aren't running the CLI yet. Are there any more > specific scenarios? > > As for the Upgrading Guides, any step up to 3.0 we doc should reference > the CLI, perhaps with a separate/additional non-CLI upgrade path that > references the plugman doc. I'd use "Upgrading Windows Phone" as a model. > > --Mike S > > ________________________________________ > From: Shazron [shaz...@gmail.com] > Sent: Tuesday, July 16, 2013 7:59 PM > To: dev@cordova.apache.org > Subject: Re: Upgrading Guides > > For https://issues.apache.org/jira/browse/CB-4222 > > I added this note at the bottom of the 2.9.0 -> 3.0.0 Upgrading Guide for > iOS: > > NOTE: Starting with Cordova 3.0.0, projects do not come with any plugins, > you will have to install the ones you require for your project using the > `plugman` CLI utility - see the Core Plugin Install Guide. > > Note the currently non-existent "Core Plugin Install Guide" which is common > for all platforms. I talked to Steve, this doc should show two methods - > the Cordova CLI way and the plugman way of how to install the core plugins. > Since the Upgrading Guides are for legacy methods, it refers to the plugman > way. > > Mike Sierra, not sure if this is a good method or we should cram everything > into the CLI doc. > > > On Tue, Jul 16, 2013 at 2:14 PM, Andrew Grieve <agri...@chromium.org> > wrote: > > > +1 document both, but we should be clear that CLI is the new fancy and > will > > eventually become the only supported (whatever that means) workflow at > some > > point in the future. > > > > > > On Tue, Jul 16, 2013 at 5:00 PM, Joe Bowser <bows...@gmail.com> wrote: > > > > > On Tue, Jul 16, 2013 at 1:41 PM, Anis KADRI <anis.ka...@gmail.com> > > wrote: > > > > I think we should document both. > > > > > > But we've already done the CLI docs. :P > > > > > > > > > > > > > > > On Tue, Jul 16, 2013 at 11:48 AM, Joe Bowser <bows...@gmail.com> > > wrote: > > > > > > > >> On Tue, Jul 16, 2013 at 6:21 AM, Andrew Grieve < > agri...@chromium.org> > > > >> wrote: > > > >> > The CLI guide reads quite well! Great work whoever put it > together! > > :) > > > >> > > > > >> > Just occurred to me that for 3.0 -> 3.1, we can probably just > write > > a > > > >> > single "CLI" upgrade guide instead of writing one for each > platform > > > >> (might > > > >> > need caveats per-platform still). > > > >> > > > > >> > Should we document how to create plugman-only projects as well as > > CLI > > > >> > projects? If so, we'll need a good top-level explainer page that > > > explains > > > >> > the difference. If not, then I don't think we should mention it in > > our > > > >> > readme. I'm hoping that we can document only the CLI flow so that > > > there > > > >> > will be less diversity in project structures out there, and it > will > > > let > > > >> us > > > >> > focus on doing one thing well. > > > >> > > > > >> > > > >> I think we should document plugman-only projects, because that's > what > > > >> exists today. It's much easier to start to use plugman for a > project > > > >> than to use the CLI, especially if you've done your own > modifications > > > >> to the Java code in your Cordova project, which a few people have > > > >> done. I see nothing here that helps our existing users maintain > their > > > >> codebases. If this project teaches you anything, it should teach > you > > > >> that just because you want people to use your project a certain way, > > > >> it doesn't mean that they will. > > > >> > > > > > >
