Providing an upgrade path is still something we need to consider. So yes, an upgrade guide that says "change the values of your plugins from x to y" is doable. As well as a script that does a global search/replace. Not rocket science.
On 3/15/13 2:19 PM, "Joe Bowser" <bows...@gmail.com> wrote: >Honestly, config.xml is a file that is going to be edited by users >now, so the last thing that I want to do is get yet another script >involved, since it could really screw up their config.xml and make >things even worse. I think we'd be better off giving them a heads up >when we release this and letting them copy and paste from our template >config.xml. > >Also, once we're done here, plugman is supposed to do this right? :P > >On Fri, Mar 15, 2013 at 2:08 PM, Simon MacDonald ><simon.macdon...@gmail.com> wrote: >> Do we provide any way to update config. Xml as all of the paths to the >> plugins will be incorrect? Possibly an update script? >> >> Simon >> On Mar 15, 2013 5:01 PM, "Joe Bowser" <bows...@gmail.com> wrote: >> >>> Hey >>> >>> Since we're working towards making the core plugins installable and >>> uninstallable, I want to go ahead and move all the plugins to a core >>> directory so that their Java namespace will be >>> org.apache.cordova.core. This means that adding and removing will be >>> less painful for scripts since they shouldn't be messing with anything >>> that's not a plugin or it's dependency. >>> >>> Any thoughts on this before I move things? This shouldn't change the >>> API at all, and things should continue to work. >>> >>> Joe >>>
