Have you tried with "mvnDebug package -Pwatch" ? You need to run in debug mode for hot code replacement to work. The best would be to run your Runner.java directly in your IDE, like Wicket Quickstart's Start.java. Combined with DCEVM it is a big time saver! But for SASS recompilation you need an external watcher, I agree.
You might be interested in http://wicketinaction.com/2014/07/build-resources-with-node.js/. You may find something useful! ;-) Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Jan 26, 2016 at 9:20 AM, Tobias Soloschenko < [email protected]> wrote: > One think I am sad of is that I had to use Jetty, because I didn't get any > response to my hot code replacement question @ tomcat mailing list. (See > Readme.md) > > With Jetty however it works flawless. > > kind regards > > Tobias > > > Am 25.01.2016 um 17:31 schrieb Martin Grigorov <[email protected]>: > > > > Nice! > > I'll take a deeper look soon! > > > > Does it support LiveReload too? I.e. change .sass/.css/ and it updates > the > > page automatically? > > > > Martin Grigorov > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jan 25, 2016 at 4:52 PM, Tobias Soloschenko < > > [email protected]> wrote: > > > >> Hi, > >> > >> I created a little showcase in which the following frameworks are > playing > >> together: > >> * Apache Wicket > >> * Apache Maven > >> * NodeJS > >> * NPM > >> * Grunt > >> * Embedded Jetty > >> * ... > >> > >> Goal was to be able to create a Wicket application with hot code > >> replacement and automated sass recompilation: > >> > >> https://github.com/klopfdreh/fluentsquare > >> > >> kind regards > >> > >> Tobias >
