This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
we need to check how compile on save (and deploy on save) interacts with javarebel agent (that is capable of reloading the classes live without a re-run/re-deploy). Also applies to frameworks like tapestry (as mentioned in #148499) we should probably somehow (how?) figure out that a technology that is using hot class replacement is in place and just copy the class files on save.
sample manual setup of netbeans maven projects, automatic IDE compilation and javarebel http://blogs.codehaus.org/people/mkleint/archives/001795_appframework_maven_javarebel_and_netbeans.html the supported IDE integration should work along those lines 1. allow embedding the javarebel execution configutation transparently 2. avoid having to place the automatic build stamp manually
When configuring actions for projects, one can reuse variables from the IDE (as defined in Tools/Variables). eg. when defining REBEL variable pointing to /home/mkleint/javatools/javarebel, then it's possible to define the Run action mapping property as follows: exec.args=-noverify -javaagent:${REBEL}/javarebel.jar -classpath %classpath ${packageClassName} when executing via exec:exec plugin (and similarly for other usecases). http://hg.netbeans.org/main/rev/1a4d55fe2b61 The added value is that the nb-actions.xml file persisted with the project doesn't hardwire the absolute path.
most probably done, I've used javarebel a few times and it seems to work (when it didn't work it was an issue in javarebel itself)