build a version of jenkins that does not bundle the plugin and then depend on that version until you are ready
On 27 April 2012 16:05, Anne Stellingwerf <[email protected]> wrote: > I'm starting to work on a extension to the subversion plugin, for which I > forked the subversion plugin. When I execute "mvn hpi:run" in the checkout > folder, I get the following info in my log: > > 27-apr-2012 15:48:02 hudson.PluginManager$1$3$1 isDuplicate >> INFO: Ignoring >> /Users/annestellingwerf/Documents/jenkins/subversion-plugin/./work/plugins/subversion.hpl >> because >> /Users/annestellingwerf/Documents/jenkins/subversion-plugin/./work/plugins/subversion.jpi >> is already loaded > > > If I want to use the (java) code I changes, I first have to go the the > plugin manager, to the installed tab, where I unpin the subversion plugin, > then go to the console from which "mvn hpi:run" as been started, and hit > enter, in order to reload the plugins. Only then i can my use changed java > code, changes in jelly are applied on reload of the webpage. > > After a new run, I have to repeat the proces of unpinning and reloading. > This is of course rather bothersome and decreasing productivity. Is this > really needed, or can this be circumvented in some way? > > Kind regards, > Anne >
