Uploaded image for project: 'JIRA Server (including JIRA Core)'
  1. JIRA Server (including JIRA Core)
  2. JRASERVER-34295

Custom Message (Mail) Handler throws exception in JIRA 6: Unable to resolve com.atlassian.jira.plugins.mail.model

    XMLWordPrintable

    Details

    • Regular Expression:
      Unable\sto\sresolve\s127\.0:\smissing\srequirement\s\[127\.0\]\spackage;\s\(package=com\.atlassian\.jira\.plugins\.mail\.model\)
    • Occurrence Factor:
      10%

      Description

      A customer reports that Custom Message (Mail) Handler written based on the development tutorial: Custom Message (Mail) Handler for JIRA that works well for JIRA 5, isn't working for JIRA 6 due to Unable to resolve com.atlassian.jira.plugins.mail.model exception with the stack trace below:

      2013-08-08 04:09:39,549 FelixDispatchQueue ERROR      [osgi.container.felix.FelixOsgiContainerManage   r] Framework error in bundle com.ni.apps.jira.mailhandler.MailHandler
      org.osgi.framework.BundleException: Unresolved constraint in bundle com.ni.apps.jira.mailhandler.Mai   lHandler [127]: Unable to resolve 127.0: missing requirement [127.0] package; (package=com.atlassian   .jira.plugins.mail.model)
              at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409)
              at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1584)
              at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:887)
              at com.atlassian.plugin.osgi.util.BundleClassLoaderAccessor$BundleClassLoader.findClass(Bund   leClassLoaderAccessor.java:69)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
              at com.atlassian.jira.plugin.DefaultComponentClassManager.constructEvenIfNotEnabled(DefaultC   omponentClassManager.java:133)
              at com.atlassian.jira.plugin.DefaultComponentClassManager.newInstance(DefaultComponentClassM   anager.java:70)
      .
      .
      .
      

      As we are unable to confirm whether or not this is indeed a bug, and being that it is out of Atlassian Support scope. We think it's best for developers to verify how vailid this is.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
                Reporter:
                takindele Taiwo Akindele
              • Votes:
                8 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: