Re: Can I develop without recompiling/restarting after every change?
Thanks for the reply -- I'll look into that option! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2227956.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Can I develop without recompiling/restarting after every change?
I'm a front-end developer trying to learn Java (total n00b) and working on a wicket application at work. The whole process feels very slow primarily because I have to recompile and restart JBoss every time I make a change. So I'm wondering what the best way is to avoid having to do this when editing .java/.js/.css/.html files during development? I'd like to just make changes and then refresh the browser to test -- is this possible? I've seen in the FAQ that you can change the application settings to auto-reload markup .html files -- where would I insert this setting (remember I'm a total n00b). As to .css/.js/.java files -- do I need jRebel or something like that to get these files to reload automatically? Thanks for helping out a super-beginner :) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
