We are happy to announce the release of License Server 3.5.0. This is the largest update the License Server has received recently.
Two years have passed since the release of JRebel 6. Throughout this time, two JRebel agents have been available in parallel (JRebel Agent and Legacy Agent). Now that the new JRebel Agent has fully matured, we are making it the default. JRebel’s support for remote servers has also been significantly enhanced. In addition, we have updated integrations with many of the frameworks and application servers to support their latest versions.
When upgrading to JRebel 7 from a previous version, check out our upgrade guide.
ZeroTurnaround is further improving the ease of use for JRebel’s Eclipse remote server users. The UI for remote server configuration has been redesigned to provide more precise control over projects.
Modern developers make use of virtual machines, cloud platforms and other remote servers to develop their applications.
JRebel eliminates redeploys by making the updated classes and resources available for the JVM and reloading the updated versions. In a local environment, this is achieved by making the JRebel agent in the JVM monitor the IDE workspace directly. With remote servers, direct monitoring is not possible — as the JVM and the IDE run in separate machines.
Spring framework support improved
This release delivers important improvements to our Spring framework support. Reloading is faster thanks to the improved file system scanning. Also, support for the
@Autowired annotation is improved: we now support editing these definitions and adding new dependencies.
We are excited to announce that for users of IntelliJ, getting started with JRebel is now easy as pie. JRebel supports multiple ways of running your application server: via IDE, from command line, or remotely (on a separate machine). We have worked hard to make sure you follow the right configuration path and don’t get lost during the setup.
As a software developer, you might not always develop apps for large enterprises with legal departments. Maybe you’ll make your own app some day, and maybe you’ll be able to let people use it in exchange for money or goods.
So what do you do after you finish developing and launching your totally-unique and innovative application? There are a lot of questions and about a billion pages of material regarding software copyrights, EULAs, contracts, licensing and everything else, but can you say with any real security what happens, and how protected you are, once you release your new baby into the wild?
NB! This post is somewhat outdated, for the complete reference on how JRebel works with Gradle, and it works marvelously, please check out the official documentation on configuring JRebel with Gradle.