torelt.blogg.se

Jrebel maven plugin configuration
Jrebel maven plugin configuration











jrebel maven plugin configuration
  1. #Jrebel maven plugin configuration install
  2. #Jrebel maven plugin configuration code

Spring Loaded is a JVM agent for reloading class file changes whilst a JVM is running. Getting Spring Loadedīefore we start with adding Spring loaded let’s take a look at what Spring Loaded can help us with. Setting it up with your IDE can be less straightforward and time-consuming. IDE tooling can also help, but has it’s limits. If you don’t have a license you will have to build, re-package and run a cargo:redeploy to get the latest changes into the running Tomcat instance. By default this archetype comes with a JRebel profile, which you can leverage if you (or your employer) already have a license. Most Hippo CMS projects start from our archetype (i.e.

jrebel maven plugin configuration

#Jrebel maven plugin configuration install

This makes it simple to use for new users, because you don’t have to install an application container first and you only need Java and Maven. Some background informationīuilding a Hippo CMS driven website is usually done with the cargo-maven2-plugin to deploy the CMS and Site (delivery-tier) application into a by Cargo created Tomcat instance. In this post I will explain how you can leverage Spring Loaded to implement your Hippo CMS project in less time. It’s battle tested, open source and free to use. Spring Loaded is used as the reloading system in Grails 2 based projects. One of these alternatives is Spring Loaded. For developers on those kinds of projects getting a JRebel license is usually a thougher challange, but don’t worry there are alternatives besides using JRebel that can also help you speed up development. For this specific scenario JRebel is excellent and it works really well, but most of the developers I meet are spending time on developing websites with Hippo CMS, which are usually less complex projects. JRebel helps limiting the amount of build, aggregate, package and redeploy cycles needed to test the changes and new features which we add to the CMS. The main reason that we use JRebel is that the the CMS suite itself is build from several multi-module Maven projects.

#Jrebel maven plugin configuration code

JRebel is a great tool and allows us to do live reloading of source code and enables us to develop the CMS product in a lot less time. At Hippo we use JRebel a lot during the development of our CMS product.













Jrebel maven plugin configuration