Remote servers feature upgraded in JRebel for NetBeans 6.5.0
Following the remote server feature updates to Eclipse and IntelliJ IDEA, we have now focused on NetBeans. JRebel for NetBeans 6.5.0 brings with it a comprehensively redesigned remote server interface and functionality.
The remote servers view
First of all, we have introduced a Remote servers view into the JRebel settings view. You can find this by opening Help > JRebel > Configuration and selecting Remote servers. From here on out, this will be the central place to manage all your remote server connections. Through this UI, you are able to add, edit, remove, enable and disable JRebel remote servers.
The idea is that these servers are reusable for all your projects. Enable the ones you want to work with at any given time. If you then synchronize your changes with JRebel (by clicking the Synchronize button on the toolbar or by enabling Synchronize on build), all the deployments of the modified projects will be updated for the servers you have enabled. With JRebel 6.5.0, you can also press the drop-down menu button next to the toolbar button for extra options and individual project synchronization.
You no longer need to define remote server URLs one-by-one for each of your remote projects (which will be a big win if you happen to work with a whole bunch of projects).
Changes to JRebel project settings
Since the remote server settings are now managed centrally in the global configuration, JRebel project settings look a lot simpler. You just have to decide whether you want to enable remote server support for a particular project. The project will then be synchronized to all remote servers that are enabled and to which this project has been deployed to. Open Window > JRebel panel and enable the remote server support for all desired workspace projects.
Automatic migration for your existing configuration
With the plugin upgrade to JRebel 6.5.0 or newer, we perform automatic migration for your old remote server configuration.
When upgrading to JRebel 6.5.0 or newer, the migration automatically converts your project setups to a workspace remote server (without the application context path, since this is no longer required). The project settings will be automatically switched to Select specific workspace servers for this project, with the relevant remote server enabled for the project. The migration is completed automatically. You are then ready to continue working with the new JRebel remote implementation!
Remote servers log
The JRebel remote server log is where you can find all the details about your remote server transactions, in case you should need them (especially if something went wrong). This way we can stop bothering you with those details in the events log and in countless IDE notifications. This console pops up automatically during remote server transactions. You can open it manually by opening Window > JRebel remote server log.