The javagent property can also be set directly from the command line without changing the project or settings.xml. For instance: mvn n -Djavaagent=-agentpath:/home/user/jrebel/lib/libjrebel64.dylib IDE plugin To run Cargo with JRebel enabled using the profile defined above, use the following command to run your project: mvn -P n -Djrebel The JRebel profile can be explicitly de-activated by running the Maven command with -P !jrebel. Otherwise rebel.xml files will be packaged with the wars of your distribution. Note: When you are ready to create a project distribution, be sure you have a clean build without the JRebel profile activated. Open cms/target/classes/rebel.xml and site/target/classes/rebel.xml to see how JRebel is configured. JRebel descriptors for both CMS and site are generated, which means that class files and resources from either project are configured to be monitored for changes. To generate the JRebel descriptors, build your project using the following command: mvn verify -Djrebel This profile is activated by specifying the property jrebel. The Bloomreach Experience Manager Project POM provides a profile dedicated to generating and enabling JRebel while building and running a Bloomreach Experience Manager project. agentpath:/home/user/jrebel/lib/libjrebel64.dylib To use the JRebel Agent when running the project locally with Cargo, set the javaagent property in your ~/.m2/settings.xml Maven configuration settings or project.
After downloading and unpacking, configure the JRebel Agent according to the settings found in the JRebel documentation. If you want to speed up this development cycle, then JRebel is a great tool to make that happen.
Jrebel eclipse tomcat code#
Please refer to the documentation of the third-party development tool for the latest installation, configuration, and usage instructions.īuilding your web application and redeploying it every time you want to see the effects of the changes you made to your project's source code can be a time consuming process. Bloomreach cannot guarantee this documentation is up to date with the latest release of the third-party development tool. This documentation describes the use of a third-party development tool and is maintained by Bloomreach on a best-effort basis.
0 kommentar(er)
