Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-41177

Code Macro Plugin offers update in Confluence 5.5. but is incompatible

      Summary

      In Confluence 5.5.x when going to > Add-ons, Code Macro Plugin offers a message to upgrade to a newer version (from 2.1.3 to 2.2.4). This new version doesn't work and generates errors in the log.

      Other Add-Ons are also listed, and may also be broken.

      Environment

      Steps to Reproduce

      1. Go to > Add-ons
      2. Confirm there's an Update button for Code Macro Plugin
      3. Click Update

      Expected Results

      Plugin is updated to 2.2.4
      or
      No option to update

      Actual Results

      Message appears
      The below exception is thrown in the atlassian-confluence.log file:

      2016-03-24 13:07:51,461 ERROR [UpmAsynchronousTaskManager:thread-2] [atlassian.plugin.loaders.ScanningPluginLoader] deployPluginFromUnit Unable to deploy plugin 'com.atlassian.confluence.ext.newcode-macro-plugin' from 'Unit: /home/jrichards/atlassian/data/atlassian-confluence-5.5/plugins-cache/1458785271319plugin.8528292429045245180.newcode-macro-plugin-2.2.4.jar (1458785271000)'.
       -- referer: http://jrichards.office.atlassian.com:8090/plugins/servlet/upm | url: /rest/plugins/1.0/ | userName: jrichards
      2016-03-24 13:07:51,463 ERROR [UpmAsynchronousTaskManager:thread-2] [atlassian.plugin.loaders.ScanningPluginLoader] deployPluginFromUnit Because of the following exception:
       -- referer: http://jrichards.office.atlassian.com:8090/plugins/servlet/upm | url: /rest/plugins/1.0/ | userName: jrichards
      com.atlassian.plugin.PluginParseException: Unable to scan for host components in plugin classes
      

      Notes

      Confluence 5.7.5 does not offer to update the Code Macro Plugin

      Workaround

      1. Stop Confluence
      2. Run this to confirm data is in the table
        select plugindataid, pluginkey, filename, lastmoddate from plugindata where pluginkey = 'com.atlassian.confluence.ext.newcode-macro-plugin';
        
      3. If there's only one row where pluginkey is com.atlassian.confluence.ext.newcode-macro-plugin run
        delete from plugindata where pluginkey = 'com.atlassian.confluence.ext.newcode-macro-plugin';
        
      4. Delete all the files in the plugin cache (with rm -fr):
        • /var/atlassian/application-data/confluence/bundled-plugins
        • /var/atlassian/application-data/confluence/plugins-cache
        • /var/atlassian/application-data/confluence/plugins-osgi-cache
        • /var/atlassian/application-data/confluence/plugins-temp
        • /var/atlassian/application-data/confluence/bundled-plugins_language
      5. Restart Confluence

      or

      1. Go to https://marketplace.atlassian.com/plugins/com.atlassian.confluence.ext.newcode-macro-plugin/versions
      2. Download version for 2.1.4
      3. Go to > Add-ons
      4. Click upload
      5. Add newcode-macro-plugin-2.1.4.jar and upload

            [CONFSERVER-41177] Code Macro Plugin offers update in Confluence 5.5. but is incompatible

            Thanks for the quick fix. FWIW: tested and confirmed.

            Stefan Hett added a comment - Thanks for the quick fix. FWIW: tested and confirmed.

            Minh Tran added a comment -

            Dear All,

            I updated the compatibility for Code Macro to 5.5.x and 5.7.x
            Version 2.2.4 will be compatible to Confluence 5.8.x to above only

            Best regards,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - Dear All, I updated the compatibility for Code Macro to 5.5.x and 5.7.x Version 2.2.4 will be compatible to Confluence 5.8.x to above only Best regards, Minh Tran Confluence BugMaster Atlassian

            Another workaround which I used was to use UPM and re-upload the compatible 2.1.4 version via the "Upload addon" link. That seemed to work fine here and I didn't have to manually tweak the database.

            Stefan Hett added a comment - Another workaround which I used was to use UPM and re-upload the compatible 2.1.4 version via the "Upload addon" link. That seemed to work fine here and I didn't have to manually tweak the database.

              Unassigned Unassigned
              jrichards@atlassian.com James Richards
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: