The live reloading doesn't depend on anything eclipse specific - it's a tapestry feature. As long as your compiled classes end up in a container that supports it (e.g. in the past, I've had problems w/ live reloading and Tomcat), you should be OK.
The "Compile on Save" feature in NetBeans is something that you definitely want to enable in your project properties - this is what compiles the classes and would put them where the servlet container needs them (make sure that you don't do "Deploy on Save" as that completely removes the need for tapestry live reloading as it uses integration w/ the servlet container) . Are you using native NetBeans projects or are you working w/ NetBeans and Maven projects (btw, both should work, but probably slightly differently) ? Cheers, Alex K On Tue, Aug 2, 2011 at 12:08 PM, earroyoron <earroyo...@yahoo.com> wrote: > First, I am sorry this email was sent to dev@tapestry list too, it was my > fault! > > The message was: > > Hi all! > > I am starting to use Tapestry,… impressive framework! > > I am developing an application, using eclipse, and I had some problems with > DerbyDB. I prefer Netbeans to do some things, and I could resolve my "derby > affair" with the NetBeansIDE. > > But now I was still using NB and, I, … is my fault or the live reloading > feature does not work when you are using NBeans? I edit a file (java or tml) > and it is not updated in jetty, and it works when using eclipse! > > Does the live reloading uses some eclipse "thing"? > > Thanks! > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
