JRebel Plugin Configuration Tab is missing
Tagged: plugin tab
April 13, 2017 at 12:56 pm #62470
with JRebel 7.0.4 the Plugin Configuration Tab (Eclipse) was removed. The changelog lists that change as an “improvement”. Why was this tab removed? I don’t see there any improvement.
How are JRebel Plugins configured now? Have i dig into a hidden configuration file?
DanielApril 13, 2017 at 1:58 pm #62471
By default JRebel automatically enables/disables whatever plugins are relevant for your environment. The only reason to manually disable a plugin is when the user is encountering a bug related to the plugin and it should only be disabled as a temporary work around while a fix is being worked on.
More often then not we were running into issues where users were disabling plugins when they should not be. This could break reloading or potentially cause errors with JRebel.
Is there a reason that you need to enable/disable JRebel plugins regularly?
ColtonApril 13, 2017 at 2:30 pm #62473
no, not really, but we used the configuration tab to add and activate our custom JRebel Plugin. The underlying question is: How to add custom JRebel Plugins that are not part of the JRebel Installation Package?
Inside the jrebel.properties File rebel.plugins is configured:
If i change true to false i would expect a log message during application startup that reads like:
The following plugins are disabled at the moment: * our plugin plugin (rebel.ourplugin_plugin)
But there is no log message like this. Any ideas?
DanielApril 19, 2017 at 2:13 pm #62516
So I had a chance to quickly test this out today to make sure everything is still working as expected with the custom plugin configuration. I downloaded our sample plugin from here.
Inside my jrebel.properties I have added the following two lines:
When I start my Tomcat server I am now seeing the following in the JRebel banner on startup:
2017-04-19 10:06:46 JRebel: The following plugins are disabled at the moment: 2017-04-19 10:06:46 JRebel: * JRebel Plugin Template (rebel.jr-plugin-template)
Is it possible that you have a typo in your properties file that is causing the plugin to not correctly be added?
ColtonApril 19, 2017 at 3:13 pm #62518
thx for testing! That put me in the right direction :). The plugins id (getId()) was different then the one named inside the jrebel.properties.
Missing my configuration tab… ;)
Thank you!April 25, 2017 at 7:40 pm #62555
I have been talking with the PM for the IDE plugins. We are at least going to update the plugin information to make it a little more clear on exactly how to add JRebel plugins through CLI, since it is a little rough to understand currently.
We are also going to consider adding a UI element to the IDE to allow users to import custom plugins via the IDE. We need to do more research on how widely custom plugins are used by our customers to determine how useful this kind of feature would be.
You must be logged in to reply to this topic.