I /think/ that 2) got some improvement in the maven-hpi-plugin itself (seem to remember some commits from Stephen talking about it IIRC). But indeed that requires to explicitly update its version in your pom, or run the fully qualified maven CLI (and not hpi:run alone).
That's also why I like the plugin-pom since it's gonna make it easier to update the plugin-pom version w/o bumping the jenkins core requirement itself. And so being able to take a recent m-hpi-p version on a more regular basis than now. And yeah, it personally bothers me sometimes. Got to try the JRebel set up I guess. 2016-02-03 8:47 GMT+00:00 Michael Neale <[email protected]>: > "write more tests and restart from time to time" seems to be pretty good > practice! (buy a faster machine too!). > > I wasn't sure if I was missing out in some way, but it seems many don't > bother with the hot reloading options. > > On Wednesday, February 3, 2016 at 7:32:28 PM UTC+11, Gavin Mogan wrote: >> >> I've had one plugin that worked with #2, I've done #1 a few times. >> Usually write more tests and restart from time to time. >> >> On Tuesday, February 2, 2016 at 3:41:57 PM UTC-8, Michael Neale wrote: >>> >>> I am curious how much people use of the hot-reloading during plugin >>> development. >>> >>> As mentioned on >>> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial - jelly and >>> other files are reloaded (I know that works well in my experience) however >>> its the other reloading that seems to be suspect when I try it (have tried >>> a few different plugins to ensure its just not one version of core etc). >>> >>> 1) there is JVM hotswap with debugging (always a mixed bag) >>> 2) press ENTER on mvn hpi:run to reload webapp >>> 3) jrebel with OSS licence >>> >>> What do people use? I have found 2 actually breaks hard almost always >>> (various errors). >>> 3 I have never tried. >>> >>> Or do people just build and run unit tests and rerun mvn hpi:run as >>> needed? >>> >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/92e542f8-8aba-443e-a999-b29bd3066bc5%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/92e542f8-8aba-443e-a999-b29bd3066bc5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6D8y-Mc%2BXxOV7qOmwwcvXjA6MdxLUXTBzkKVNaz2cVeg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
