|Internal Discussion Link:||/|
we currently run development in an Eclipse Indigo environment supported by a Maven 2 (through the command line) to built all supporting file structures for Jive. Deployment of Jive SBS is performed via Maven and Jive plugins are uploaded via the Jive SBS service directly (admin interface). Our backend consists of a XAMPP based MySQL database.
Every time a new plugin is deployed to the Jive SBS service, a restart of the service is required. Every time a plugin needs to be removed and substituted it is required to restart is one time for the removal and one time again for the next upload. This is a very time consuming enterprise since and costs about 10 minutes every time. I assume that using a plugin-upload directory will not spare the restart of the Jive service and I currently do not know any better way to do a much faster and a much simpler plugin deploy.
I am wondering if there is a better way to do faster deployment in a setting that is entirely focused on development. What do you guys do to develop Plugins efficiently?
While customizations are outside of the scope of Support you can post your question in our Developers space to gain feedback from the community should you wish.
Are you using our Maven project? If not, please see Maven: How To Create a New Maven Project for information.
Also, please see Build and Run Your Local Jive Customization which includes the following:
Adding plugins to your Jive instance is easy. In a UAT or production environment, you would do it using the admin console, and then restart the server. You could do that locally, as well, but would take a wicked long time to get anything done. When you install a plugin via the admin console, the uploaded plugin JAR file is stored in the database. When the system is restarted, the plugin is retrieved, decoded, and exploded into memory for quick access. That said, every time you do a plugin install, you have to restart your server. That, plus multiple trips to the admin console to uninstall/install plugins, makes for a poor use of your time.
So as soon as you compile, your plugin update is available to your SBS instance, and only a restart is required to update it.
Additionally, with this configuration, FTL and CSS changes do not require a restart.