Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B53649304 for ; Mon, 11 Jun 2012 20:50:11 +0000 (UTC) Received: (qmail 38634 invoked by uid 500); 11 Jun 2012 20:50:11 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 38605 invoked by uid 500); 11 Jun 2012 20:50:11 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 38597 invoked by uid 99); 11 Jun 2012 20:50:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 20:50:11 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates 64.18.1.189 as permitted sender) Received: from [64.18.1.189] (HELO exprod6og105.obsmtp.com) (64.18.1.189) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 20:50:03 +0000 Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob105.postini.com ([64.18.5.12]) with SMTP ID DSNKT9ZZ5LQwVyXYVs3yCdKJ6ORkCmbJqwhT@postini.com; Mon, 11 Jun 2012 13:49:42 PDT Received: from inner-relay-1.corp.adobe.com (inner-relay-1.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q5BKncX9003310; Mon, 11 Jun 2012 13:49:39 -0700 (PDT) Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q5BKnbvn013318; Mon, 11 Jun 2012 13:49:38 -0700 (PDT) Received: from SJ1SWM219.corp.adobe.com (10.5.77.61) by nahub01.corp.adobe.com (10.8.189.97) with Microsoft SMTP Server (TLS) id 8.3.192.1; Mon, 11 Jun 2012 13:49:37 -0700 Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by SJ1SWM219.corp.adobe.com ([fe80::d55c:7209:7a34:fcf7%12]) with mapi; Mon, 11 Jun 2012 13:49:37 -0700 From: Filip Maj To: "callback-dev@incubator.apache.org" , "alunny@gmail.com" Date: Mon, 11 Jun 2012 13:50:21 -0700 Subject: Re: Plugin Format and Spec Thread-Topic: Plugin Format and Spec Thread-Index: Ac1IE7Z0ms7JFgK1RJShnS6a2i33dQ== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Nice work Andrew! I suggest taking this and moving to a cordova wiki page (assuming all committers are on board to adopting this as the basis for a plugin spec) Is target-dir necessary for the element? For Java files, the tooling could take a peak inside the .java file and extract out the package name from the file, no? Phonegap build already does this doesn't it? Adding the ability to modify existing parts of a native platform's config document to the portion might be needed.. Although Ive yet to dig up a use case. Will dig around more. +1 agree that and is redundant. Tooling should be able to distinguish this so merging with makes a lot of sense. Looking good! On 6/8/12 6:40 PM, "Andrew Lunny" wrote: >Hi all, > >I've posted to this list before about pluginstall[1], the tool I've >developed as part of working on PhoneGap Build and requiring programmatic >installation of Cordova plugins. > >I've now written up a spec for the format that pluginstall uses - I think >it's generally useful for Cordova plugin installation and manipulation. >The >spec is available on GitHub: >https://github.com/alunny/cordova-plugin-spec > >Issues and/or pull requests and/or forks welcome. > >Cheers, >Andrew > >[1] https://github.com/alunny/pluginstall