This is common pattern, you must have your own repo and cut your own internal release of the plugin with your fixes. Then bug the maintainer to commit it, however the more tests you put in your patch, the quicker it is committed.
-Dan On Sat, Dec 26, 2009 at 1:05 AM, Trevor Harmon <[email protected]> wrote: > One of my projects depends on a couple of third-party plugins available on > Central. These plugins provide key functionality for the build, but they also > contain some serious bugs. Let's say I fix these bugs myself and submit > patches to the maintainers. It could be months before the patches are > reviewed, committed, and eventually show up as a new plugin release on > Central. > > I certainly can't wait around for my patches to be applied, so what are my > options in the meantime? Should I simply install the patched plugin locally? > Or would it be better (for any definition of that word) to set up my own > repository manager and deploy them there? > > Thanks, > > Trevor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
