The CLI treats the platform code as a build artifact. While this is
the goal, the reality is that people modify the code, and people rely
on old plugins. There will be users who NEVER use the CLI because of
this fact, and will need to use plugman. Just because you want to
have people use the software in a particular way doesn't mean that
they will, and we should provide some support for people who want to
not use the CLI. I don't use the CLI, because I actually work with
the platform source on a regular basis and I don't want to constantly
destroy and rebuild the project that I hooked the framework source to.
I know that people will say that I'm a special case, but the bug
tracker says otherwise. Also, we have CordovaWebView, which is a
component that isn't even supported with the CLI flow. Just because
the CLI is the new hawtness doesn't mean that we should neglect
everyone who chooses to actually hack Cordova into something they
want.
On Wed, Jul 17, 2013 at 11:36 AM, Carlos Santana <csantan...@gmail.com> wrote:
> Do we need to expose "plugman"? or can we just talk about CLI
>
> Its my understanding that everything can be done with CLI (plugin
> [{add|remove|rm} <PATH|URI>] )
>
> The simpler the better in my opinion.
>
> These two statements contradict to me as noobie (I assume we want to
> advertise cordova 3.0.0 first one with official cli support)
> - No way to upgrade existing CLI projects
> - Plugman for existing projects,
>
> most people should not have existing CLI projects, I vote to keep it simple
> and generic
> Create a new cordova project using CLI, then use upgrade guide to merge
> your existing cordova project with new 3.0.0 generated project.
>
>
>
>
>
> On Wed, Jul 17, 2013 at 2:16 PM, Brian LeRoux <b...@brian.io> wrote:
>
>> I'll do a draft and send a review out sometime this afternoon.
>>
>>
>> On Wed, Jul 17, 2013 at 11:01 AM, Andrew Grieve <agri...@chromium.org>
>> wrote:
>> > I've been hit with some pretty unplanned baby duties today, so don't
>> expect
>> > to have much time today to work. I would like to urge someone to take
>> > ownership of this task though.
>> >
>> > Thoughts on what we should say:
>> >
>> > - Snapshot available on [[download page]]
>> > - Introducing new command line tools: plugman & CLI
>> > - Plugman for existing projects, CLI for those wanting a cross-platform
>> > project
>> > - Both tools are new, so please expect some and file bugs on [[JIRA]]
>> > - Links to upgrade guides
>> > - Core plugins no longer exist by default in new projects
>> > - Can create your own plugins via [[plugin guide / plugman spec]]
>> > - Known Issues:
>> > - <merges> to change soon
>> > - whitelist format will be unified soon, but isn't yet
>> > - IDE's show generated files
>> > - No way to upgrade existing CLI projects
>> > - Anything else?
>> >
>> >
>> >
>> >
>> > On Tue, Jul 16, 2013 at 5:07 PM, Andrew Grieve <agri...@chromium.org>
>> wrote:
>> >
>> >> Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276
>> >>
>> >> Will update the wiki once we're through this release (to flesh out the
>> >> process)
>> >>
>> >> Thank YOU Carlos!
>> >>
>> >>
>> >> On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana <csantan...@gmail.com
>> >wrote:
>> >>
>> >>> The Cordova Blog is live
>> >>>
>> >>> http://cordova.apache.org/#news
>> >>> You can use your RSS reader to subscribe
>> >>>
>> >>> A new blog post needs to be added when cutting a new release
>> >>>
>> >>> The step should be added to the Wiki (but I don't access)
>> >>> https://wiki.apache.org/cordova/CuttingReleases
>> >>>
>> >>> A tasks you be added to the JIRA item for announcing release (but I
>> can't
>> >>> find the JIRA #)
>> >>>
>> >>> I want to thank Andrew with putting up with me on setting up the blog,
>> me
>> >>> being a noob to the Cordova community
>> >>>
>> >>> --
>> >>> Carlos Santana
>> >>> <csantan...@gmail.com>
>> >>>
>> >>
>> >>
>>
>
>
>
> --
> Carlos Santana
> <csantan...@gmail.com>
