• Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Low Low
    • None
    • 2.4.3
    • None

      The FishEye Atlassian Notifier plugin described on http://blogs.atlassian.com/developer/2009/10/dragon_slayer_supplement_action_issues_with_commit_commands.html no longer works, see http://forums.atlassian.com/thread.jspa?messageID=257368087

      2011-02-16 07:48:55,031 ERROR [main] com.atlassian.plugin.osgi.factory.OsgiPlugin com.atlassian.plugin.osgi.factory.OsgiPlugin-enableInternal - Detected an error (BundleException) enabling the plugin 'com.atlassian.notifier.core' : Unresolved constraint in bundle com.atlassian.notifier.fisheye-plugin [39]: Unable to resolve 39.0: missing requirement [39.0] package; (package=com.thoughtworks.xstream).  This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package. For more details on how to fix this, see http://confluence.atlassian.com/x/1xy6D
      2011-02-16 07:48:55,033 ERROR [main] com.atlassian.plugin.manager.PluginEnabler com.atlassian.plugin.manager.PluginEnabler-enable - Unable to enable plugin com.atlassian.notifier.core
      com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.atlassian.notifier.core
              at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:410)
              at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:237)
              at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:90)
              at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:682)
              at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:170)
              at com.atlassian.fisheye.plugin.DelegatingFisheyePluginManager.onApplicationEvent(DelegatingFisheyePluginManager.java:113)
              at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
              at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
              at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
              at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
              at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
              at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:383)
              at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
              at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
              at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
              at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
              at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
              at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
              at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
              at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
              at com.cenqua.fisheye.web.jetty.FishEyeWebApplicationContext.doStart(FishEyeWebApplicationContext.java:27)
              at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
              at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
              at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
              at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
              at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
              at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
              at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
              at org.mortbay.jetty.Server.doStart(Server.java:224)
              at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
              at com.cenqua.fisheye.web.WebServer.start(WebServer.java:274)
              at com.cenqua.fisheye.ctl.Run.mainImpl(Run.java:234)
              at com.cenqua.fisheye.ctl.Run.main(Run.java:69)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)
              at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:113)
              at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41)
      Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.atlassian.notifier.fisheye-plugin [39]: Unable to resolve 39.0: missing requirement [39.0] package; (package=com.thoughtworks.xstream)
              at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409)
              at org.apache.felix.framework.Felix.startBundle(Felix.java:1709)
              at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
              at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892)
              at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:382)
              ... 38 more
      

            [CRUC-5624] Fix the FishEye Atlassian Notifier plugin

            Hi Pedro,

            You can install Apache Maven 2.1.0 and run the mvn install goal to build and deploy it locally.

            Alternatively the JAR is available from our public mvn repository:

            https://maven.atlassian.com/content/groups/public/com/atlassian/notifier/notifier-fisheye-plugin/2.3.3/

            cheers,
            Tim

            Tim Pettersen (Inactive) added a comment - Hi Pedro, You can install Apache Maven 2.1.0 and run the mvn install goal to build and deploy it locally. Alternatively the JAR is available from our public mvn repository: https://maven.atlassian.com/content/groups/public/com/atlassian/notifier/notifier-fisheye-plugin/2.3.3/ cheers, Tim

            Strike me as dumb, but how should i proceed to compile that code?
            not familiarized with maven... Can I have a binary to test?

            Pedro Storti added a comment - Strike me as dumb, but how should i proceed to compile that code? not familiarized with maven... Can I have a binary to test?

            Hi Jason,

            thanks for your fast respoonse. I just tried to compile version 2.3.3-SNAPSHOT and it seems to work now - at least the plugin is integrated into FishEye now and the final test shows "201 CREATED" (as described in the blog).
            That means this bug can be closed with the release of 2.3.3 of the notifier-plugin.

            Many thanks for your help!

            Bernhard

            Bernhard J. M. Grün added a comment - Hi Jason, thanks for your fast respoonse. I just tried to compile version 2.3.3-SNAPSHOT and it seems to work now - at least the plugin is integrated into FishEye now and the final test shows "201 CREATED" (as described in the blog). That means this bug can be closed with the release of 2.3.3 of the notifier-plugin. Many thanks for your help! Bernhard

            Hi,

            You can find the source of the notifier plugins here:

            https://studio.atlassian.com/svn/NOT/trunk

            It should have anon read only access. If you have any issues I can send you a zip of the source

            Cheers,

            Jason

            jhinch (Atlassian) added a comment - Hi, You can find the source of the notifier plugins here: https://studio.atlassian.com/svn/NOT/trunk It should have anon read only access. If you have any issues I can send you a zip of the source Cheers, Jason

            Is there any entry point I could start fixing that issue? Maybe I could fix it by myself as I really need that plugin for our FishEye-JIRA interconnection.

            Bernhard J. M. Grün added a comment - Is there any entry point I could start fixing that issue? Maybe I could fix it by myself as I really need that plugin for our FishEye-JIRA interconnection.

            AntonA added a comment -

            Hi,

            Unfortunately, at the moment we do not know the fix. We would need to have a thorough look at the problem. However, we are working through quiet a few more urgent issues and therefore may not be able to look at this for some time.

            I apologize for not being able to help. You may wish to try posting to the FishEye & Crucible Dev Forum:
            http://forums.atlassian.com/forum.jspa?forumID=127
            where other users may help.

            Cheers,
            Anton

            AntonA added a comment - Hi, Unfortunately, at the moment we do not know the fix. We would need to have a thorough look at the problem. However, we are working through quiet a few more urgent issues and therefore may not be able to look at this for some time. I apologize for not being able to help. You may wish to try posting to the FishEye & Crucible Dev Forum: http://forums.atlassian.com/forum.jspa?forumID=127 where other users may help. Cheers, Anton

            I've just tried to create a plugin JAR that contains the classes of xstream too.
            After restarting FishEye 2.5.2 again there appears an error message that some more classes (by atlassian) are missing.
            Do you have an idea how to fix that problem such that one can use FishEye/JIRA commit commands?

            Bernhard J. M. Grün added a comment - I've just tried to create a plugin JAR that contains the classes of xstream too. After restarting FishEye 2.5.2 again there appears an error message that some more classes (by atlassian) are missing. Do you have an idea how to fix that problem such that one can use FishEye/JIRA commit commands?

            TimP added a comment -

            We should check why xstream is no longer exported and potentially bundle it in the plugin itself.

            TimP added a comment - We should check why xstream is no longer exported and potentially bundle it in the plugin itself.

              Unassigned Unassigned
              tom@atlassian.com Tom Davies
              Affected customers:
              5 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: