Netbeans module development with JRebel
In [project]\nbproject\platform.properties add the following line
run.args.extra=-J-noverify -J-javaagent:e:/tools/jrebel/jrebel.jar -J-Drebel.log=true
Note:
- This requires a proper installation of jrebel in the path
e:/tools/jrebel/ - Do not forget to generate a
rebel.xmlinto the root of your classpath - You have to compile the changed java source manually by
Menu->Run->Compile file(“Compile-on-save” is not yet available for netbeans modules) - There will be some OSGI-exceptions when running/debugging the application, but class reloading works properly.
Tested with NetBeans IDE 7.1 RC2 (Build 201111302200)+7.1, JRebel 4.5.3
Other resources: http://blogs.codehaus.org/people/mkleint/2009/07/maven-netbeans-platform-javare.html
Update: You can also have a look at Javeleon
Update 2: In maven-based nbms you can run modules the following way
- enable “compile on save”
-
generate
rebel.xmlto/src/mainusing the context menu of jrebel (this way it will be copied totarget/classes) - alter the properties-section of the
pom.xmllike this
<properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <netbeans.run.params.ide/> <netbeans.run.params>-J-noverify -J-javaagent:e:/tools/jrebel/jrebel.jar -J-Drebel.log=true ${netbeans.run.params.ide}</netbeans.run.params> </properties> - run the module the normal way – you will accounter some osgi-exception as mentioned above
- make changes to your classes and jrebel will pick it up like
[207230] JRebel: Reloading class 'b2s.compare.clipboard.TextDiffer'. - small issue: the jrebel-messages do not appear on the output-window – but in
jrebel.log
Recent Comments