com.atlassian.plugin.PluginParseException

Class version is incompatible with current JVM: com.metova.confluence.ThemeHelper

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web46

  • via Atlassian JIRA by Matt Ryall, 11 months ago
    Class version is incompatible with current JVM: com.metova.confluence.ThemeHelper
  • via Atlassian JIRA by Matt Ryall, 1 year ago
    Class version is incompatible with current JVM: com.metova.confluence.ThemeHelper
  • via Ecosystem JIRA by Tablus jira_support@tablus.com, 1 year ago
    Class version is incompatible with current JVM: com.atlassian.jira.plugin.ext.subversion.issuetabpanels.changes.SubversionRevisionsTabPanel>com.atlassian.plugin.PluginParseException: Class version is incompatible with current JVM: com.atlassian.jira.plugin.ext.subversion.issuetabpanels.changes.SubversionRevisionsTabPanel
  • Stack trace

    • com.atlassian.plugin.PluginParseException: Class version is incompatible with current JVM: com.metova.confluence.ThemeHelper at com.atlassian.plugin.descriptors.AbstractModuleDescriptor.init(AbstractModuleDescriptor.java:75) at com.atlassian.confluence.plugin.descriptor.VelocityContextItemModuleDescriptor.init(VelocityContextItemModuleDescriptor.java:24) at com.atlassian.plugin.parsers.XmlDescriptorParser.createModuleDescriptor(XmlDescriptorParser.java:147) at com.atlassian.plugin.parsers.XmlDescriptorParser.configurePlugin(XmlDescriptorParser.java:85) at com.atlassian.plugin.loaders.ClassLoadingPluginLoader.deployPluginFromUnit(ClassLoadingPluginLoader.java:99) at com.atlassian.plugin.loaders.ClassLoadingPluginLoader.addFoundPlugins(ClassLoadingPluginLoader.java:151) at com.atlassian.confluence.plugin.DatabaseClassLoadingPluginLoader.addFoundPlugins(DatabaseClassLoadingPluginLoader.java:116)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.