search

bluepapa32 / gradle-watch-plugin

Gradle Watch Plugin
Apache License 2.0
117 stars 20 forks source link

Is this plugin dead? Any alternatives? #23

Open joh-klein opened 9 years ago

joh-klein commented 9 years ago

Is this plug-in still actively maintained? If not, what are the alternatives or is a fork more current? There haven't been any comments from the developer on open issues. And PR are not merged either. This really is too bad, since it is a very helpful plugin!

antony commented 9 years ago

It also doesn't seem to work on Gradle 2.6.

bkputnam commented 9 years ago

I ran into the 2.6 issue too. I think the only major thing that's necessary to get this working with 2.6 is to upgrade the gradle wrapper (there were also some minor issues with checkstyle after the upgrade). I've got a pull request that I think does everything necessary here: https://github.com/bluepapa32/gradle-watch-plugin/pull/24.

Andy-L commented 9 years ago

That fix looks like it modifies the build of the plugin itself to work with gradle 2.6 What @antony is talking about is that the plugin doesn't work with a project that is using gradle 2.6.

bkputnam commented 9 years ago

Right. I don't entirely understand why upgrading the plugin's build system to 2.6 causes it to work on other projects that use gradle 2.6, but that has been my experience so far.

cunhaax commented 8 years ago

Stop using the plugin, gradle 2.5 supports this http://gradle.org/feature-spotlight-continuous-build/

bkputnam commented 8 years ago

Thanks for the link, I didn't know about that feature. Reading through the docs it seems like that will cover a majority of use cases, but unfortunately not mine (yet). I've implemented a hot-reload feature with this plugin that works with jettyRunWar. They touch on that in the "Future Improvements" section at the end. Since these release notes are for 2.5, I searched through the 2.6 and 2.7 release notes as well, but I didn't see anything about non-Play hot-reload features (I would be happy to be corrected if I missed something).

Here's the relevant bit from the link you posted:

In the next release (2.6), Play support is coming to Gradle, and with that you’ll be able to start Play applications in a separate JVM for local development. With continuous build enabled, Gradle will hot-reload the Play application whenever classes or assets are changed. The Play plugin accomplishes this by registering the Play JVM with Gradle in a way that survives between builds.

We want to eventually evolve this Play specific reload functionality into a general feature, so plugins can have their own “hot-reload”-like behavior.