Private static final String WEBLOGIC_JAVA_OPTS_KEY = "JAVA_OPTIONS" Thanks a lot, this indeed gave me an important hint! : ) Decompiling your source and creating some ugly hack is of course another option, but maybe there is a "proper" way of doing this.? I would really appreciate if somebody familiar with this plugin's implementation could please drop me comment on that one : ). so there seems to be no super-obvious place to manipulate with to add extra JVM arguments.
key=server-id, value=Oracle WebLogic Server 10gR3 at localhost key=attr-weblogic-initialized, value=true key=attr-start-script, value=startWebLogic.sh when i iterate over the arguments that your plugin has set, i get something like that: This doesn't seem to work for the weblogic server startup, though. For normal java apps and for tomcat for example i can do this by adding my stuff to the ILaunchConfigurationWorkingCopy attributes with the key ".VM_ARGUMENTS". I managed to extend your tab-group with my own tab for setting up JRebel, but now the problem is how exactly could I implement setting new JVM-options so that they would get set when the weblogic server is actually started. Using Eclipse, Jrebel eclipse setup is done and rebel.xml is generating successfully. So I am looking for a way to extend your Enterprise pack, specifically the .ui plugin that draws the tab-group "Oracle Weblogic Launch Configuration" in the "Run Configurations" window. I am trying to setup Jrebel for Hybris 6.1 in my local. I am a dev from ZeroTurnaround (and currently working on JRebel Eclipse plugin to provide better JRebel integration with the Eclise WTP, including the case when running a Weblogic server from inside Eclipse. If there is, maybe somebody could forward it for me, or tell me who should i get in touch with? : ) I know this forum is more like a user forum and that this is more of a developer-question, but as far as i know there is no better place to post this question.
If someone needs the configuration files details down't hesitate asking. Also had to use the fabulous Maven Copy Plugin because the xslt transformation occurred after the final war packaging and I had to add the resulting rebel.xml to that WAR.
#Jrebel setup generator#
I used the XSLT Generator Maven Plugin to help me merge the various rebel.xml files. This is becoming another issue a bit different of the original question :) Maybe I should through another question. So these kind of properties will not be enough to guarantee that the absolute paths generated on each developer machine in the rebel.xml are correct.įor now, I'm trying to tackle using some kind of maven plugin to do the rebel.xml merge. I'm using maven properties but we've have two different maven multi-module hierarchy that don't know about each other and I can't use a root pom to connect them.
But this is worthless for my team development environments. I can get it work if I create a custom rebel.xml for the main webapp that points to all the absolute directories containing the source files (static files such as JSP, HTML, JS, CSS, images, etc.) of the depending web apps. The rebel.xml for the jars modules are at the right places (inside the jar file). Because the rebel.xml it's generated dynamically via jrebel maven plugin when the main webapp build occurs, only the it's jrebel.xml prevail. I have a main web app module that depends on several webapps modules. Kind of.I'm still struggling with the war modules overlaying. What is a funcional development environment involving maven eclipse and a external tomcat?.It's possible to over come that eclipse WTP issue?.Currently, the Tomcat instance is controlled via service (tomcat monitor) and the deployed web apps are configured with a XML located at $/target/app will do the trick). I'm having a hard time getting JRebel to work in my current development environment.