The translation assistance plugin is already bundled in the jenkins.war. So if you restart Jenkins, it always loads the translation plugin from the war. You can change that behaviour, if you go to the installed plugins page, look for the translation assistance plugin and click the button "Unlock" or something like that. Then you should be able your own version of the plugin.
Regards, Manuel On Fri, Mar 23, 2012 at 11:43, Paul Schwann <[email protected]> wrote: > Hi Jan, > > Thanks for your reply! > > Based on your message, I started playing with the different ways of plugin > updates and with the Jenkins installation itself. What I notices is the > following: > Before changing anything, [jenkins]\plugins\ contains a translation.jpi with > time stamp 3/23/12 9:39 and a folder translation. > > I manually upload the 1.9 hpi of the "Translation Assistance Plugin". In the > installation folder [jenkins]\plugins there is still a file translation.jpi > but now with timestamp 3/23/12 11:34 This is somehow what I would expect > since I uploaded the file (with *hpi extension though). > > I restart Jenkins and now, translation.jpi has the former timestamp again > 3/23/12 9:39. So apparently, the update has no effect and simply was > ignored. > > Next try: > I shut down Jenkins, remove the [jenkins]\plugins\translation.jpi and the > [jenkins]\plugins\translation folder. I restart Jenkins and the folders > reappear. > > Where do they come from? Is it possible that Jenkins simply overrides > anything which I upload/update while starting? > > I must do something fundamentally wrong... > > Regards, > Paul >
