Changeset 7226 for trunk/www/admin/extensions/wizard.jsp

Timestamp:

Nov 15, 2016, 1:35:33 PM (7 years ago)

Author:

Nicklas Nordborg

Message:

References #2041: Support for extension points within extensions

Adding more debug logging to see what it going on when scanning for updated extensions.

If using the ExtensionsFile.wasModified() method instead of the ExtensionsFile.checkModified() method (which has already been called in the ExtensionsControl.scanForChanges() method) changes in one extension will automatically be detected in other extensions depending on the same JAR file (this was implemented in [7192] and [7196]).

However it only works once. If the server admin simply closes the extension installation wizard and then open it again, only the JAR file that was actually changed will be detected and not those that depend on it.

I'll need to set up a better test case. One idea is to add an example extension point to the "Example code package" (​http://baseplugins.thep.lu.se/wiki/net.sf.basedb.examplecode) that we can use for testing purposes from other extensions.

File:

• trunk/www/admin/extensions/wizard.jsp (modified) (1 diff)

trunk/www/admin/extensions/wizard.jsp

@@ -118 +118 @@
           checkInstall = true;
         }
-        else if (xtFile.checkModified())
+        else if (xtFile.wasModified())
         {
           status = "Modified";