Actually, on second thought, no, let's keep the compatibility classes in for now. We may want to keep using this namespace post-3.0. I think I misunderstood what was being asked.
On Tue, Jul 9, 2013 at 2:28 PM, Joe Bowser <bows...@gmail.com> wrote: > On Mon, Jul 8, 2013 at 12:50 PM, Andrew Grieve <agri...@chromium.org> wrote: >> Want to bring this up again. >> >> There was a bit of discussion on the bug: >> https://issues.apache.org/jira/browse/CB-4038 >> >> I've already gone ahead with creating backward-compatiblity classes in the >> .api namespace, but I think it would be better to just delete them. >> >> Main points in favour: >> 1. For 3.0, people will need to do some work to their plugins anyways (add >> plugin.xml + refactor their JS into modules comes to mind) >> 2. The change to plugins is trivial. Just replace all occurrences of >> "import org.apache.cordova.api" with "import org.apache.cordova". >> > > I'm OK with it for now, only because we don't have the time to > formalize the Android Plugin API. I would have liked to keep the api > separation but perhaps we can revisit this 3.1 or 3.2.
