No problems, I thought that you might be busy thats why I had a look into doing it myself. And I got to the error message and thought I might need some commit access that I didn't have but thought that I would check.
Anyhow I think there could be a choice to use a local Selenium artifact or just use the bundled versionis one way to approach the problem, then its up to the user to upgrade this. Whether that works or not is scales is not something I know though. Sorry. Look forward to have a look at the fixes you do! Thanks. Tim. On Friday, 11 January 2013 13:12:39 UTC+1, DarkRift wrote: > > You need to have access to the macen repo to commit in there. > > > Sorry for being that much busy and not able to fix all those bugs in > plugin (maintaining that plugin is not an assignment of my job, only on my > free time) > > I was trying to remove the library dependency, but I can't seem to find a > good way ... > > I'll try to commit my latest changes and release a new version this > weekend that will at least cover the bugs I currently fix from v2.2 > > I could also commit 2.28 at the same time and change the dependency, > unless I find the right way to remove it conpletely and have it upgradable > by itself... Maye if I create another plugin just for the dependency so it > can upgrade itself ... Dunno yet how to handle that problem. > > Any thoughts ? > >
