I'm irritated by this change but not enough to -1 it. This has gone through our deprecation timeline and it's not like we decided on the new XML yesterday. I don't understand why we can't meet our own deadlines. Will this be gone by 3.0? If not, why not. On May 16, 2013 2:30 PM, "Filip Maj" <[email protected]> wrote:
> Filed 3416: https://issues.apache.org/jira/browse/CB-3416 > > Affects only android and iOS on master. > > On 5/16/13 1:30 PM, "Jesse" <[email protected]> wrote: > > >+1, and another point: make sure your native bits continue to load from > >both <plugin/> and <feature/> until the deprecation window slams shut. > > > >@purplecabbage > >risingj.com > > > > > >On Thu, May 16, 2013 at 12:56 PM, Benn Mapes <[email protected]> > wrote: > > > >> +1 to leave in an empty <plugin/> until deprecation time is reached, it > >> just makes sense. > >> > >> > >> On Thu, May 16, 2013 at 12:51 PM, Gorkem Ercan <[email protected] > >> >wrote: > >> > >> > +1 for a deprecation period > >> > > >> > -- > >> > Gorkem > >> > > >> > > >> > On Thu, May 16, 2013 at 3:45 PM, Filip Maj <[email protected]> wrote: > >> > > >> > > We deprecated this recently. Can we leave an empty <plugins> > >>element in > >> > > config.xml for each platform while the deprecation window is still > >> open? > >> > > This way tooling such as plugman can still add <plugin> elements > >>while > >> > the > >> > > platforms still support it. > >> > > > >> > > Once we fully remove <plugin> support then IMO that is the right > >>time > >> to > >> > > completely remove the <plugins> element from config.xml. > >> > > > >> > > Also makes life easier for services consuming cordova (*cough* > >>PhoneGap > >> > > Build *cough*). :) > >> > > > >> > > Lemme know what you guys think. > >> > > > >> > > > >> > > >> > >
