Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of bowserj@gmail.com designates
 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABiQX1UtNpKKgprkZFPh7ZmzbvRyx1wRecB4NKKhPxQct83rgg@mail.gmail.com>
References: 
 <CAM1AYQB9xv66uJxsC0+9284WZ2PpyjY_e5bDc0emuYfFH=JaJg@mail.gmail.com>
	<CE09922C.2264D%fil@adobe.com>
	<CABiQX1UtNpKKgprkZFPh7ZmzbvRyx1wRecB4NKKhPxQct83rgg@mail.gmail.com>
Date: Mon, 15 Jul 2013 12:20:25 -0700
Message-ID: 
 <CAOBL_k7BhuhafmUg43rHMMQ9De7pXTPkzy8=cv+ep+uMeg-QPg@mail.gmail.com>
Subject: Re: Plugin packages on Android
From: Joe Bowser <bowserj@gmail.com>
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jul 15, 2013 at 12:14 PM, Andrew Grieve <agrieve@chromium.org> wrote:
> -1 to shims. A plugin's java package name shouldn't be considered a part of
> its API. That's why there is a mapping in the config.xml.
>
> Shouldn't have to change any require() statements, or any JS at all. Those
> use plugin IDs, not java namespaces.

If this is really true, then I don't see why we don't wait until the
next release.

> Replace-all on the package statement at the top of the file, and change the
> reference in plugin.xml. I'd put this change in the "polish" category.
> That's what we should be doing now, no?

I think we have enough work already without adding this extra polish.
This is the only release where we have a deadline, and I think that
adding this will make us miss that deadline.