Well, you learned that the Instrumentation API exists and it offers redefinition of classes as an operation. So then it is time to rethink you initial premise of “the JVM actually not allowing to change the definition of classes that have already been loaded”. You should note that as the...
Ok, the answer is: indeed it is not possible to configure more than one directory under the <web><link target="/"></link></web> configuration. I have now a folder ./target/all-webapp where I smylink (cp -sR) all files via gradle task ... not nice but works ... and thank god jrebel is following symlinks!
java,eclipse,mercurial,atlassian-sourcetree,jrebel
you should just add the .metadata folder to your mercurial ignore list. If you've already committed the file to your repo, then you need to do something like this: hg remove -Af .project Stop tracking from the context menu I think does the same thing....
The client side doesn't need anything special. The server side though requires the RequestFactory and all its RequestContext and proxies hierarchy to be processed by the validation tool. From the command line, in the context of the archetypes, that means launching the process-classes phase on the *-server module, e.g. mvn...
eclipse,maven,ant,jrebel,jetty-9
Of course. JRebel doesn't depend on Maven. What you need is to make sure that rebel.xml configuration file is deployed with the application - the JRebel will be able to locate the resources (i.e. classes and static HTML/JS/CSS files). Make sure that rebel.xml ends up in WEB-INF/classes of the WAR...
java,spring,spring-boot,jrebel
If your project is using embedded container, it should have main method. I would try to run it as Java application. According to Spring Boot docs, JRebel should work....
spring,spring-boot,jhipster,jrebel
This error occurred when I use Jrebel to 6.0.0 after updating Jrebel version to 6.1.0, I got this error org.springframework.boot.context.embedded.tomcat.ServletContextInitializerLifecycleListener - Error starting Tomcat context: org.springframework.beans.factory.BeanCreationException and I solve this by add -XX:MaxPermSize=512m at VM Arguments (eclipse) thanks to ZT (zeroturnaround) Support...
eclipse,tomcat,jrebel,eclipse-marketplace
Open up your Tomcat run configuration and in the VM arguments delete the ${jrebel_args} bit.
Depending on standalone or deployment configuration that you are using, the war file may be sitting in the respective content directory. Check the question related to content directory here Also check the last segment stanalone.xml or domain.xml which will have information on the content directories.
spring,intellij-idea,jboss7.x,wicket,jrebel
Change the deployment artifact from 'war' to 'war exploded' did the job.
jrebel.jar is packaged inside the JRebel plugin for IntelliJ IDEA. It doesn't have to be deployed with the WAR itself. JRebel plugin will set the correct JVM parameters to the command line when you start via "Run with JRebel" or "Debug with JRebel": -javaagent:/path/to/jrebel.jar You don't have to do it...
Both DCEVM and JRebel are meant for development environments only. DCEVM works fine in many use cases, it can load most of the class changes and is perfect if you are on budget and need basic reload capability. In comparison JRebel works with over 100 frameworks like Spring, Hibernate etc...
java,tomcat,ssh,intellij-idea,jrebel
JRebel features Remoting facility, which can be used to sync the changes via HTTP to the remote machine. For that, you should enable JRebel on remote Tomcat (via -javaagent:jrebel.jar) and enable JRebel remote plugin that create an HTTP endpoint for negotiating with the IDE plugin. -Drebel.remoting_plugin=true will do. For more...
maven,jetty,embedded-jetty,maven-jetty-plugin,jrebel
I have luckily found the answer in the Maven configuration page (where i call jetty:run) and it works. For those who will also need this and use the JRebel Eclipse plugin, here is the answer: (I would still be appreciated if someone knows a better way. Maybe in pom.xml, in...
java,spring,maven-jetty-plugin,jrebel
Updating to the latest version fixed the problem it seems there is an issue with the 5.5 version of jrebel and now I am using the latest 6.2.1 Release build and the errors are gone. Solution is to Download the latest standalone version of Jrebel and configure the jrebel.jar in...
spring,spring-boot,jhipster,jrebel
I solve this problem by add -XX:MaxPermSize=512m at VM Arguments (eclipse) thanks to ZT (zeroturnaround) Support...
spring,maven,datasource,placeholder,jrebel
This can happen if you're using resource filtering with JRebel, as the application looks up the bean's xml in its unfiltered form from the project working directory (as per rebel.xml). To resolve this, you'll need to update rebel.xml for that module, adding exclude for that particular XML file - see...
JRebel works with Karaf, really the best thing to do is just try it out. Depending on how you're running your app (in the IDE vs command line) you may need to add the JAVA_OPTS yourself. The IDE plugin can generate them for you.