Changes between Version 6 and Version 7 of PluginDevelopmentGuide

Timestamp:

08.04.2013 02:07:09 (12 years ago)

Author:

jri

Comment:

Redeploy the plugin

PluginDevelopmentGuide

@@ -39 +39 @@
 == The plugin turn-around cycle ==
 
-This section illustrates how to begin a plugin project, how to build and how to deploy a plugin, and how to re-deploy the plugin once you made changes in its source code. In other words, this section illustrates the plugin development turn-around cycle.
+This section illustrates how to begin a plugin project, how to build and how to deploy a plugin, and how to redeploy the plugin once you made changes in its source code. In other words, this section illustrates the plugin development turn-around cycle.
 
 Let's start with a very simple plugin called //DeepaMehta 4 Tagging//. This plugin will just create a new topic type called `Tag`. Once the plugin is activated the topic type will appear in the DeepaMehta Webclient's //Create// menu, so you can create tag topics and associate them with arbitrary topics. And you will be able to fulltext search for tags.
@@ -207 +207 @@
 
 In another terminal:
+
 {{{
 #!sh
@@ -301 +302 @@
 The result so far: the //DeepaMehta 4 Tagging// plugin provides a new topic type definition or, in other words: a data model. All the active operations on the other hand like create, edit, search, delete, associate, and navigate are provided by the DeepaMehta Webclient at a generic level, and are applicable to your new topic type as well.
 
+=== Redeploy the plugin ===
+
+Once you've made any changes to the plugin files, you have to build the plugin again. Just like before in the plugin terminal:
+
+{{{
+#!sh
+mvn clean package
+}}}
+
+Once building is complete the changed plugin is redeployed automatically. You'll notice activity in the DeepaMehta terminal:
+
+{{{
+#!txt
+Apr 8, 2013 1:10:40 AM de.deepamehta.core.osgi.PluginActivator stop
+INFO: ========== Stopping plugin "DeepaMehta 4 Tagging" ==========
+Apr 8, 2013 1:10:40 AM de.deepamehta.core.impl.PluginImpl removeService
+INFO: Removing DeepaMehta 4 core service from plugin "DeepaMehta 4 Tagging"
+Apr 8, 2013 1:10:40 AM de.deepamehta.core.impl.PluginImpl removeService
+INFO: Removing Web Publishing service from plugin "DeepaMehta 4 Tagging"
+Apr 8, 2013 1:10:40 AM de.deepamehta.core.impl.PluginImpl removeService
+INFO: Removing Event Admin service from plugin "DeepaMehta 4 Tagging"
+...
+...
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.osgi.PluginActivator start
+INFO: ========== Starting plugin "DeepaMehta 4 Tagging" ==========
+...
+...
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.impl.PluginManager activatePlugin
+INFO: ----- Activating plugin "DeepaMehta 4 Tagging" -----
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.impl.PluginImpl createPluginTopicIfNotExists
+INFO: Installing plugin "DeepaMehta 4 Tagging" in the database ABORTED -- already installed
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.impl.MigrationManager runPluginMigrations
+INFO: Running migrations for plugin "DeepaMehta 4 Tagging" ABORTED -- everything up-to-date (migrationNr=1)
+...
+...
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.impl.PluginManager activatePlugin
+INFO: ----- Activation of plugin "DeepaMehta 4 Tagging" complete -----
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.impl.PluginManager checkAllPluginsActivated
+INFO: ### Bundles total: 33, DeepaMehta plugins: 17, Activated: 17
+Apr 8, 2013 1:10:44 AM de.deepamehta.core.impl.PluginManager activatePlugin
+INFO: ########## All Plugins Activated ##########
+Apr 8, 2013 1:10:44 AM de.deepamehta.plugins.webclient.WebclientPlugin allPluginsActive
+INFO: ### Launching webclient (url="http://localhost:8080/de.deepamehta.webclient/") ABORTED -- already launched
+...
+}}}
+
+In contrast to the initial build of the plugin you can recognize some differences in this log:
+
+* The old version of the plugin currently deployed is stopped.
+* The new version of the plugin is deployed (that is //started// and //activated//) right away.
+* The plugin is //not// installed again in the database as already done while initial build.
+* The migration is //not// run again as already done while initial build.