Previously, when I ran mvn jenkins-dev:run the instance was running and the Jelly view (and re-compiled classes) were reloaded automatically.

Since the 2.152 and the PR#3758, the things changed. The documentation cannot be used any longer.

On 2.152+:

• mvn jenkins-dev:run starts the instance but the hot reload feature does not work, even after pressing enter (was not required before). At least the jelly views are the ones from src.
• mvn jenkins-dev:run -f war starts the instance but with the jelly views packaged in the war during a previous mvn clean install -DskipTests. No hot reload.

After the migration, the mvn jenkins-dev:run is no longer working for 2.151- instances, the log hangs at "Started Jetty Server" forever. I am forced to run with -f war now in order to make it working.

Request: please re-enable the hot reload feature.

Ping oleg_nenashev and olamy for their Jetty knowledge.

Acceptance criteria

• understand the reason this was originally patched
• fix the issue...