cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John M. Wargo" <jwarg...@gmail.com>
Subject Re: Created a plugin to help with local plugin development
Date Tue, 20 Jan 2015 01:34:26 GMT
You're probably right, but it seems to make sense to include it for consistency sake.

On 1/14/2015 7:40 PM, Shazron wrote:
> I noticed that sometime ago - my thinking is, there is no more context
> (.opts.plugin object) really after the plugin is uninstalled, that's why
> the hook is not there.
>
> On Wed, Jan 14, 2015 at 4:27 PM, Wargo, John <john.wargo@sap.com> wrote:
>
>> Looking at the Hooks read me at
>> https://github.com/apache/cordova-lib/blob/master/cordova-lib/templates/hooks-README.md.
>> Looks like after_plugin_uninstall is missing from the list.   I'm assuming
>> it's supposed to be there? Let me know and I'll make the change.
>>
>> John M. Wargo
>>
>> -----Original Message-----
>> From: Michal Mocny [mailto:mmocny@google.com]
>> Sent: Monday, December 1, 2014 2:14 PM
>> To: dev
>> Subject: FYI: Created a plugin to help with local plugin development
>>
>> Took the opportunity to use our new plugin hooks and created a plugin to
>> automate a tedious task I've been doing a lot of recently: plugin
>> re-installation.
>>
>> https://github.com/mmocny/cordova-plugin-plugin-auto-upgrade
>>
>> As per the README:
>> ================
>>
>> This plugin with automatically upgrade (re-install) a set of plugins
>> (specified by you) before every cordova prepare. This is useful if you are
>> doing plugin development and would like to automatically synchronize your
>> app with any changes made to your plugin.
>>
>> Install the plugin: cordova plugin add
>> org.apache.cordova.labs.pluginAutoUpgrade
>>
>> At root of your app, create a pluginAutoUpgrade.json file, which looks
>> like:
>>
>> {
>>    "PLUGIN_ID": "PLUGIN_INSTALL_PATH",
>>    "PLUGIN_ID2": "PLUGIN_INSTALL_PATH"
>> }
>>
>> ================
>>
>> This is useful if you are making changes to a plugin inside the plugin's
>> directory structure.
>>
>> For more meaty plugin work, you are possibly better off making native
>> changes inside platforms/ and js changes inside plugins/, and being very
>> careful to not clobber your work (or use the build/run scripts directly to
>> skip prepare entirely).  I'm considering improving that workflow as well.
>>
>> For now, I've found this plugin useful for minor plugin work.  Sharing in
>> case you do, too.
>>
>> -Michal
>>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message