![]() It might not be for everyone, but if you are a bits and pieces person like myself, this might be for you. My approach means A LOT of updated deploys - but this, for those of you who are not familiar, is where JRebel comes into the game. Me? I tend to be the bits and pieces type developer - I know what I want to achieve but I take it one bite at a time. ![]() The other part was that he like to think of it as a sort of game of compiler roulette, taking his chances and hoping that everything worked. One part of his reasoning for this was because he hated waiting for deployments. I remember working with a guy who would spend hours writing thousands of lines of code before he compiled it. Last we'll wrap it up by showing how to configure/generate the rebel.xml file - specifically how to manage this for the new Gradle project structure. Next we'll setup our agent configuration and logging levels stuff so that you can use to reveal some additional logging and help you figure out whether or not things are working. If you already know about JRebel, you can skip that section. First, for any JRebel newcomers, I'm going to do a quick "What is JRebel". In this post I'm going to share what I found and what I did in hopes that it will shortcut this task for others. The short answer is no, youl use JRebel, and, for me, I think there is still heaps of value in the tool. ![]() So my question was, with the new model and all this OSGI stuff, "Does this mean I can't or don't need JRebel anymore?". Liferay 7's achitecture is - let's say - is "a bit of a shift" from the past versions, so I wasn't sure. I started doing some research as well as having a chat with the infamous David Nebinger about JRebel, OSGI, whether or not it should in theory work etc. I am a huge JRebel fan myself and, based on what I know of JRebel and how it works, couldn't think of a reason why it wouldn't work - but, I hadn't yet tried it out. This is what the JRebel banner should look like:I recently responded to the thread in the forums where the poster was asking about Liferay 7 and it's compatibility with OSGI. When successful, you will see the JRebel banner in the console right at server startup. You can find more help for setting JRebel up with a remote server over here. ![]() Not running your server remotely Follow another application server startup method. Follow the instructions provided to set up JRebel for your remote application server.Pick your desired Java, target environment and operating system.This is what the JRebel banner should look like: When successful, you will see the JRebel banner in the console right at server startup. You can find the same command line instructions in the JRebel reference manual. Not running your server from a command line? Follow another application server startup method. Follow the instructions provided to set up JRebel for your application server.Pick your desired Java and target environment.Open Help > JRebel > Configuration > Startup.12:19:20 JRebel: Licensed to ZeroTurnaround. 12:19:20 JRebel: at least 0 redeploys/restarts saving you about 0 hours. 12:19:20 JRebel: Over the last 1 days JRebel prevented 12:19:20 JRebel: (c) Copyright ZeroTurnaround AS, Estonia, Tartu. This is what the JRebel banner should look like: When successful, you will see the JRebel banner in the console right at server startup. Not running your server from the IDE? Follow another application server startup method. ![]() To debug your application with JRebel, press the Debug with JRebel button instead.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |