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 ? On 2013-01-11, at 04:13, Tim Child <[email protected]> wrote: > I am trying to fork the selenium plugin to upgrade the Selenium version used. > (Eventually I would like to commit some much needed documentation as well). > > But I am getting a problem because http://repo.jenkins-ci.org/public/ doesn't > have the correct, I think, artifact of selenium-server-standalone:jar. Which > at the time of writing should be 2.28.0 > (http://code.google.com/p/selenium/downloads/detail?name=selenium-server-standalone-2.28.0.jar > to be exact). > > How do I go about getting that in > http://repo.jenkins-ci.org/public/org/seleniumhq/selenium/selenium-server-standalone/ > Or does someone with commit access need to do this? > > Thanks in advance, > > Tim.
