One method that I've used is with cordova-cli. You can point cordova-cli
to use a local copy of a particular platform implementation. So, I would
clone down and check out the 3.0 branch for cordova-ios, android, etc.
Create a project with `cordova create tmp`. Edit tmp/.cordova/config.json
so it has this structure:
{
lib:{
android:{
id:'cordova-with-no-plugins',
version:'3.0',
uri:'/Users/fil/src/cordova-android'
}
}
}
So in the above example, I am telling cordova-cli to look under
/Users/fil/src/cordova-android for cordova-android and use it instead of
what comes standard with cordova-cli.
Then if I run:
`cordova platform add android`
It will use my custom location for cordova-android to create a project. At
that point, I can `cordova plugin add
https://git-wip-us.apache.org/repos/asf/cordova-plugin-whatever.git` to
install any of the core broken-out plugins.
On 6/25/13 2:10 PM, "Steven Gill" <stevengil...@gmail.com> wrote:
>Hey Don,
>
>Currently, all of the platform repos have 3.0 branches. These branches
>have
>the plugins ripped out. You can run the usual creates scripts for each
>platform to create a project. You would then use plugman to install the
>plugins into your created projects.
>
>Anis is working on a discovery mechanism for plugins currently.
>
>You can take a look at
>http://github.com/brianleroux/plugin-breakout-release-test-harness/ to see
>how we have been testing all of the plugins.
>
>-Steve
>
>
>On Tue, Jun 25, 2013 at 11:56 AM, Don Coleman <don.cole...@gmail.com>
>wrote:
>
>> Has anyone documented the process for building Cordova 3.0 for
>>development?
>>
>> I see all the cordova-plugin-* repos. Is there a base project with
>>build
>> scripts?
>>
