[JSWSERVER-139] Integrate Links Hierarchy plugin into GreenHopper

Shaun Clowes (Inactive) added a comment - 26/Sep/2012 12:06 AM

diz: The Links Hierarchy plugin was not developed by Atlassian, was never a part of GreenHopper and has never been supported. The GreenHopper team does not have the bandwidth to take it on, so we are keen for any interested users to take it on. The Structure plugin is a much more capable plugin that is supported and maintained by ALMWorks.

On the other hand, the GreenHopper team is currently working on Epic support in GreenHopper which will allow an Epic -> Story -> Task hierarchy. We hope that this will meet the needs of many users.

Thanks,
Shaun

Shaun Clowes (Inactive) added a comment - 26/Sep/2012 12:06 AM diz : The Links Hierarchy plugin was not developed by Atlassian, was never a part of GreenHopper and has never been supported. The GreenHopper team does not have the bandwidth to take it on, so we are keen for any interested users to take it on. The Structure plugin is a much more capable plugin that is supported and maintained by ALMWorks. On the other hand, the GreenHopper team is currently working on Epic support in GreenHopper which will allow an Epic -> Story -> Task hierarchy. We hope that this will meet the needs of many users. Thanks, Shaun

Mike Eldridge added a comment - 25/Sep/2012 8:44 PM

What a cop-out. Bad form, Nicholas.

Mike Eldridge added a comment - 25/Sep/2012 8:44 PM What a cop-out. Bad form, Nicholas.

Nicholas Muldoon [Atlassian] added a comment - 12/Jan/2012 10:41 PM

Hi Steffen,

Great to hear you are keen to contribute to the LHR plugin!

The latest code is available here. Unfortunately, it looks like JC built 1.1 and did not check in so those changes are now lost forever - the main change was the switch to the GreenHopper LinkProvider Plugin Module.

Thank you.

Regards,
Nicholas Muldoon

Nicholas Muldoon [Atlassian] added a comment - 12/Jan/2012 10:41 PM Hi Steffen, Great to hear you are keen to contribute to the LHR plugin! The latest code is available here . Unfortunately, it looks like JC built 1.1 and did not check in so those changes are now lost forever - the main change was the switch to the GreenHopper LinkProvider Plugin Module . Thank you. Regards, Nicholas Muldoon

Steffen Stundzig [stundzig.it] added a comment - 12/Jan/2012 11:37 AM

hi jean-christophe,

there are a problem with jira4.4 and your plugin. I would fix it, but in the atlassian svn I couldn't find the latest sources for the 1.1 release of your plugin. Could you send me the sources or could you update the svn please?

regards

Steffen Stundzig [stundzig.it] added a comment - 12/Jan/2012 11:37 AM hi jean-christophe, there are a problem with jira4.4 and your plugin. I would fix it, but in the atlassian svn I couldn't find the latest sources for the 1.1 release of your plugin. Could you send me the sources or could you update the svn please? regards

Gary Murphy added a comment - 15/Dec/2011 5:53 PM

I am using version 1.1 of the Links Hierarchy plugin with version Jira 4.4/Greenhopper 5.7.1 I get the same errors as Chris. It works OK but we get the annoying ERROR messages in the log.

Looks like we either download and fix or evaluate "Structure" at http://structure.almworks.com/

Gary Murphy added a comment - 15/Dec/2011 5:53 PM I am using version 1.1 of the Links Hierarchy plugin with version Jira 4.4/Greenhopper 5.7.1 I get the same errors as Chris. It works OK but we get the annoying ERROR messages in the log. Looks like we either download and fix or evaluate "Structure" at http://structure.almworks.com/

Chris Kent added a comment - 15/Nov/2011 12:53 AM

Hi,
I am running JIRA 4.4.3, with Greenhopper 5.8.2 and Links Hierarchy 1.1 and my system seems to be running alright, no obvious problems, however I am getting these errors in the log file and Hercules is referring me to this issue...

2011-11-15 11:37:54,753 http-8080-4 ERROR chrisk 697x984x1 10yyx85 10.115.1.4 /secure/VersionBoard.jspa [pyxis.jira.greenhopper.GreenHopperMenuItems] java.lang.NullPointerException
2011-11-15 11:38:05,229 http-8080-4 ERROR chrisk 698x985x1 10yyx85 10.115.1.4 /secure/VersionBoard.jspa [pyxis.jira.greenhopper.GreenHopperMenuItems] java.lang.NullPointerException
2011-11-15 11:38:24,023 http-8080-4 ERROR chrisk 698x1003x1 10yyx85 10.115.1.4 /secure/VersionBoard.jspa [pyxis.jira.greenhopper.GreenHopperMenuItems] java.lang.NullPointerException

What should I do?

Chris Kent added a comment - 15/Nov/2011 12:53 AM Hi, I am running JIRA 4.4.3, with Greenhopper 5.8.2 and Links Hierarchy 1.1 and my system seems to be running alright, no obvious problems, however I am getting these errors in the log file and Hercules is referring me to this issue... 2011-11-15 11:37:54,753 http-8080-4 ERROR chrisk 697x984x1 10yyx85 10.115.1.4 /secure/VersionBoard.jspa [pyxis.jira.greenhopper.GreenHopperMenuItems] java.lang.NullPointerException 2011-11-15 11:38:05,229 http-8080-4 ERROR chrisk 698x985x1 10yyx85 10.115.1.4 /secure/VersionBoard.jspa [pyxis.jira.greenhopper.GreenHopperMenuItems] java.lang.NullPointerException 2011-11-15 11:38:24,023 http-8080-4 ERROR chrisk 698x1003x1 10yyx85 10.115.1.4 /secure/VersionBoard.jspa [pyxis.jira.greenhopper.GreenHopperMenuItems] java.lang.NullPointerException What should I do?

Nancy Belser added a comment - 31/Oct/2011 1:47 PM

FYI. I am using version 1.1 (available on plugins.atlassian.com) of the Links Hierarchy plugin with version Jira 4.4.3/Greenhopper 5.7.4. Still seems to work.

Nancy Belser added a comment - 31/Oct/2011 1:47 PM FYI. I am using version 1.1 (available on plugins.atlassian.com) of the Links Hierarchy plugin with version Jira 4.4.3/Greenhopper 5.7.4. Still seems to work.

Nicholas Muldoon [Atlassian] added a comment - 29/Mar/2011 12:32 AM

Hello,

I am closing this issue as Won't Fix.

The original author of the Links Hierarchy Report plugin no longer works for Atlassian. Without that persons experience and knowledge of the code it is non-trivial to migrate and implement this functionality into GreenHopper.

All existing feature requests and bugs for the Links Hierarchy Report plugin have been moved over to the open source project.

Next steps:

If you are interested and willing to contribute to this plugin grab the source code and get involved.
You can continue to use the Links Hierarchy Report plugin. There are no known issues with JIRA 4.3.
Structure is a commercial plugin for JIRA which provides n-level hierarchies and a great visualisation of this hierarchy. I recommend you take a look.

Thank you.

Regards,
Nicholas Muldoon

Nicholas Muldoon [Atlassian] added a comment - 29/Mar/2011 12:32 AM Hello, I am closing this issue as Won't Fix. The original author of the Links Hierarchy Report plugin no longer works for Atlassian. Without that persons experience and knowledge of the code it is non-trivial to migrate and implement this functionality into GreenHopper. All existing feature requests and bugs for the Links Hierarchy Report plugin have been moved over to the open source project . Next steps: If you are interested and willing to contribute to this plugin grab the source code and get involved . You can continue to use the Links Hierarchy Report plugin. There are no known issues with JIRA 4.3. Structure is a commercial plugin for JIRA which provides n-level hierarchies and a great visualisation of this hierarchy. I recommend you take a look. Thank you. Regards, Nicholas Muldoon

Jim McCaskey added a comment - 13/Dec/2010 8:14 PM

We are using Beta 2 on Jira 4.2.1 with out any issues as far as we can tell. I do want to make a minor change to it (to view the Tree View by Default) but can't seem to track down the latest source. The source at the below link appears to be for Beta 2.

https://studio.plugins.atlassian.com/source/browse/JLHR/

Jim McCaskey added a comment - 13/Dec/2010 8:14 PM We are using Beta 2 on Jira 4.2.1 with out any issues as far as we can tell. I do want to make a minor change to it (to view the Tree View by Default) but can't seem to track down the latest source. The source at the below link appears to be for Beta 2. https://studio.plugins.atlassian.com/source/browse/JLHR/

DaveT added a comment - 16/Nov/2010 9:35 PM

@Robert Sanders: Did you have any problems running version 1.1 of this plugin with Jira 4.2? We're about to upgrade Jira at our site as well.

In general, it's plain this plugin is getting no love at all. The SPAC page is way out of date, there's no CI build, and no way to tell if it's compatible with the latest releases short of trying it out ourselves to see what breaks.

DaveT added a comment - 16/Nov/2010 9:35 PM @Robert Sanders: Did you have any problems running version 1.1 of this plugin with Jira 4.2? We're about to upgrade Jira at our site as well. In general, it's plain this plugin is getting no love at all. The SPAC page is way out of date, there's no CI build, and no way to tell if it's compatible with the latest releases short of trying it out ourselves to see what breaks.

Robert Sanders added a comment - 02/Nov/2010 9:09 PM

Just upgraded to JIRA 4.2 the other day. I will try installing manually, but the UPM doesn't return any results when searching for this plugin. It strikes me that integrating this plugin into Greenhopper would make a lot of sense.

Robert Sanders added a comment - 02/Nov/2010 9:09 PM Just upgraded to JIRA 4.2 the other day. I will try installing manually, but the UPM doesn't return any results when searching for this plugin. It strikes me that integrating this plugin into Greenhopper would make a lot of sense.

Ben Speakmon [Atlassian] added a comment - 06/Jul/2010 10:42 PM

The PAC editor was missing the toolbar buttons to edit links inside of descriptions. I've deployed a new version with the fix and corrected the link in the description.

Ben Speakmon [Atlassian] added a comment - 06/Jul/2010 10:42 PM The PAC editor was missing the toolbar buttons to edit links inside of descriptions. I've deployed a new version with the fix and corrected the link in the description.

Deleted Account (Inactive) added a comment - 28/Jun/2010 10:28 AM

The link to this issue is wrong on this page: https://plugins.atlassian.com/plugin/details/5003
Should have been https://jira.atlassian.com/browse/GHS-139 instead of https://plugins.atlassian.com/browse/GHS-139

Deleted Account (Inactive) added a comment - 28/Jun/2010 10:28 AM The link to this issue is wrong on this page: https://plugins.atlassian.com/plugin/details/5003 Should have been https://jira.atlassian.com/browse/GHS-139 instead of https://plugins.atlassian.com/browse/GHS-139

Nikolai Dokovski added a comment - 09/Jun/2010 7:33 AM

Hi
JC the proposed solution works on JIRA 4.1. I had to modify the pom.xm, plugin xml and build against the latest SDK.
Actually I removed almost all dependencies in the pom and followed SDK practices, the result is quite simple pom structure.

Cheers
Niki

Nikolai Dokovski added a comment - 09/Jun/2010 7:33 AM Hi JC the proposed solution works on JIRA 4.1. I had to modify the pom.xm, plugin xml and build against the latest SDK. Actually I removed almost all dependencies in the pom and followed SDK practices, the result is quite simple pom structure. Cheers Niki

JC added a comment - 08/Jun/2010 4:22 PM

Awesome news Hans!

Thanks for the prompt update.
I will post it on the official page.

Cheers,
JC

JC added a comment - 08/Jun/2010 4:22 PM Awesome news Hans! Thanks for the prompt update. I will post it on the official page. Cheers, JC

Hans Menzi added a comment - 08/Jun/2010 4:15 PM

JC, the beta3 plugin works.

Thanks for your help!

Hans Menzi added a comment - 08/Jun/2010 4:15 PM JC, the beta3 plugin works. Thanks for your help!

JC added a comment - 08/Jun/2010 3:23 PM

Hi Hans,

All works fine on my environment although I found some errors in the version declarations of the plugin xml.
I have updated them to JIRA 4.1 and repackaged the plugin.
Do you think you could give it a try? It is attached to this issue.

If it does solve your issue I will post it on the official plugin page.

Thanks for your help!

Cheers,
JC

JC added a comment - 08/Jun/2010 3:23 PM Hi Hans, All works fine on my environment although I found some errors in the version declarations of the plugin xml. I have updated them to JIRA 4.1 and repackaged the plugin. Do you think you could give it a try? It is attached to this issue. If it does solve your issue I will post it on the official plugin page. Thanks for your help! Cheers, JC

JC added a comment - 08/Jun/2010 3:02 PM

Hi Hans,

Yes, the Links-hierarchy-reports-1.0-beta2 was the last version posted.
I have no problems running it on JIRA 4.1#519
I am now trying to apply the patch to see if it changes anything.

Cheers,
JC

JC added a comment - 08/Jun/2010 3:02 PM Hi Hans, Yes, the Links-hierarchy-reports-1.0-beta2 was the last version posted. I have no problems running it on JIRA 4.1#519 I am now trying to apply the patch to see if it changes anything. Cheers, JC

Hans Menzi added a comment - 08/Jun/2010 2:57 PM

JC, just want to make sure I am on the latest version. That version/build is the latest released version, correct?

Hans Menzi added a comment - 08/Jun/2010 2:57 PM JC, just want to make sure I am on the latest version. That version/build is the latest released version, correct?

JC added a comment - 08/Jun/2010 1:46 PM - edited

Hummm...

You are right!
The plugin was migrated to the new plugin platform. You did it properly in the first place ...
Let me have a quick look on JIRA 4.1#519

Will be back to you shortly

Cheers,
JC

Sorry for the confusion...

JC added a comment - 08/Jun/2010 1:46 PM - edited Hummm... You are right! The plugin was migrated to the new plugin platform. You did it properly in the first place ... Let me have a quick look on JIRA 4.1#519 Will be back to you shortly Cheers, JC Sorry for the confusion...

Hans Menzi added a comment - 08/Jun/2010 1:40 PM

Then the Install type and location is wrong on the right on this page: https://plugins.atlassian.com/plugin/details/5003 AND the big red box on this page: https://studio.plugins.atlassian.com/wiki/display/JLHR/Links+Hierarchy+Reports. Is it possible to change this information, as it is incorrect?

So I installed the plugin 1.0 way and put the jar into: "C:/Program Files/Atlassian/JIRA 4.1/atlassian-jira/WEB-INF/lib/" I get the following in my log file (the plugin is disabled). Any suggestions?

Links Hierarchy Reports : com.pyxis.jira.links.hierarchy.reports
Version : 0.7.6
Status : disabled
Reason : OSGi plugins cannot be deployed via the classpath, which is usually WEB-INF/lib.
URL is: jar:file:/C:/Program%20Files/Atlassian/JIRA%204.1/atlassian-jira/WEB-INF/lib/links-hierarchy-reports-1.0-beta2.jar!/atlassian-plugin.xml
Vendor : Pyxis technologies inc.
Description : Provides an Interactive (AJAX) Hierarchical view of linked issues.

Hans Menzi added a comment - 08/Jun/2010 1:40 PM Then the Install type and location is wrong on the right on this page: https://plugins.atlassian.com/plugin/details/5003 AND the big red box on this page: https://studio.plugins.atlassian.com/wiki/display/JLHR/Links+Hierarchy+Reports . Is it possible to change this information, as it is incorrect? So I installed the plugin 1.0 way and put the jar into: "C:/Program Files/Atlassian/JIRA 4.1/atlassian-jira/WEB-INF/lib/" I get the following in my log file (the plugin is disabled). Any suggestions? Links Hierarchy Reports : com.pyxis.jira.links.hierarchy.reports Version : 0.7.6 Status : disabled Reason : OSGi plugins cannot be deployed via the classpath, which is usually WEB-INF/lib. URL is: jar: file:/C:/Program%20Files/Atlassian/JIRA%204.1/atlassian-jira/WEB-INF/lib/links-hierarchy-reports-1.0-beta2.jar!/atlassian-plugin.xml Vendor : Pyxis technologies inc. Description : Provides an Interactive (AJAX) Hierarchical view of linked issues.

JC added a comment - 08/Jun/2010 1:29 PM - edited

Hi Hans,

Edited - see comment below
~~The link hierarchy plugin is a plugin that needs to be install in the /WEB-INF directory of your JIRA.~~
~~You will need to:~~

~~Stop JIRA~~
~~Remove the plugin from (jar) the /installed-plugins directory~~
~~Copy the plugin (jar) into the /WEB-INF directory~~
~~Restart JIRA~~

See the Usage section from Links Hierarchy Reports

Cheers,
JC

JC added a comment - 08/Jun/2010 1:29 PM - edited Hi Hans, Edited - see comment below The link hierarchy plugin is a plugin that needs to be install in the /WEB-INF directory of your JIRA. You will need to: Stop JIRA Remove the plugin from (jar) the /installed-plugins directory Copy the plugin (jar) into the /WEB-INF directory Restart JIRA See the Usage section from Links Hierarchy Reports Cheers, JC

Hans Menzi added a comment - 08/Jun/2010 1:00 PM

I am running JIRA build 4.1#519 with patch ~~JRA-21004~~, and Greenhopper 4.4.1.

When I put https://studio.plugins.atlassian.com/source/browse/~raw,r=53309/JLHR/jars/links-hierarchy-reports-1.0-beta2.jar into my installed-plugins directory (D:\JIRA_41\plugins\installed-plugins) I get the following exceptions on startup of JIRA, I have also included a screenshot from the Greenhopper admin screen that shows that the plugin is not installed.

2010-06-08 08:49:45,480 Thread-1 INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: D:\JIRA_41\plugins\installed-plugins\links-hierarchy-reports-1.0-beta2.jar (1268934304366) created
2010-06-08 08:49:46,757 Thread-1 WARN [plugin.osgi.factory.OsgiPlugin] Unable to enable plugin 'com.pyxis.jira.links.hierarchy.reports'
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.pyxis.jira.links.hierarchy.reports
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:397)
at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:237)
at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:69)
at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:550)
at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:153)
at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49)
at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1286)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:225)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:211)
at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.pyxis.jira.links.hierarchy.reports [44]: package; (&(package=com.atlassian.jira)(version>=4.0.1)(version<=4.0.1))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:363)
... 25 more
2010-06-08 08:49:46,758 Thread-1 ERROR [atlassian.plugin.manager.PluginEnabler] Unable to enable plugin com.pyxis.jira.links.hierarchy.reports
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.pyxis.jira.links.hierarchy.reports
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:397)
at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:237)
at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:69)
at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:550)
at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:153)
at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49)
at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1286)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:225)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:211)
at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.pyxis.jira.links.hierarchy.reports [44]: package; (&(package=com.atlassian.jira)(version>=4.0.1)(version<=4.0.1))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:363)
... 25 more

Hans Menzi added a comment - 08/Jun/2010 1:00 PM I am running JIRA build 4.1#519 with patch JRA-21004 , and Greenhopper 4.4.1. When I put https://studio.plugins.atlassian.com/source/browse/~raw,r=53309/JLHR/jars/links-hierarchy-reports-1.0-beta2.jar into my installed-plugins directory (D:\JIRA_41\plugins\installed-plugins) I get the following exceptions on startup of JIRA, I have also included a screenshot from the Greenhopper admin screen that shows that the plugin is not installed. 2010-06-08 08:49:45,480 Thread-1 INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: D:\JIRA_41\plugins\installed-plugins\links-hierarchy-reports-1.0-beta2.jar (1268934304366) created 2010-06-08 08:49:46,757 Thread-1 WARN [plugin.osgi.factory.OsgiPlugin] Unable to enable plugin 'com.pyxis.jira.links.hierarchy.reports' com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.pyxis.jira.links.hierarchy.reports at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:397) at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:237) at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:69) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:550) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:153) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1286) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:225) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:211) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) 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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.pyxis.jira.links.hierarchy.reports [44] : package; (&(package=com.atlassian.jira)(version>=4.0.1)(version<=4.0.1)) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263) at org.apache.felix.framework.Felix.startBundle(Felix.java:1597) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902) at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:363) ... 25 more 2010-06-08 08:49:46,758 Thread-1 ERROR [atlassian.plugin.manager.PluginEnabler] Unable to enable plugin com.pyxis.jira.links.hierarchy.reports com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.pyxis.jira.links.hierarchy.reports at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:397) at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:237) at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:69) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:550) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:153) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1286) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:225) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:211) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) 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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.pyxis.jira.links.hierarchy.reports [44] : package; (&(package=com.atlassian.jira)(version>=4.0.1)(version<=4.0.1)) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263) at org.apache.felix.framework.Felix.startBundle(Felix.java:1597) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902) at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:363) ... 25 more

JC added a comment - 07/Jun/2010 5:04 AM - edited

The current beta version does not break for me in JIRA 4.1
links-hierarchy-reports-1.0-beta2.jar

[Edited]
This version was posted on the Plugin page a few months ago.

Cheers,
JC

JC added a comment - 07/Jun/2010 5:04 AM - edited The current beta version does not break for me in JIRA 4.1 links-hierarchy-reports-1.0-beta2.jar [Edited] This version was posted on the Plugin page a few months ago. Cheers, JC

JC added a comment - 02/Jun/2010 2:46 PM

Hi Matt,

I havent looked at it yet.
As soon as GH 5.0 is out the door I will spent some time on it.
It shouldnt take too long I think. By early next week it should be JIRA 4.1 compatible.

Cheers,
JC

JC added a comment - 02/Jun/2010 2:46 PM Hi Matt, I havent looked at it yet. As soon as GH 5.0 is out the door I will spent some time on it. It shouldnt take too long I think. By early next week it should be JIRA 4.1 compatible. Cheers, JC

MattS added a comment - 02/Jun/2010 2:34 PM

Or to put it another way, which parts of this plugin do not work with JIRA 4.1?

MattS added a comment - 02/Jun/2010 2:34 PM Or to put it another way, which parts of this plugin do not work with JIRA 4.1?

MattS added a comment - 02/Jun/2010 2:26 PM - edited

JC,

Are you expecting 4.1 support to be difficult? I have a number of customers who use this plugin, since there is a link to it from an official Atlassian product! Perhaps I could help with the work?

Best wishes,

~Matt

MattS added a comment - 02/Jun/2010 2:26 PM - edited JC, Are you expecting 4.1 support to be difficult? I have a number of customers who use this plugin, since there is a link to it from an official Atlassian product! Perhaps I could help with the work? Best wishes, ~Matt

JC added a comment - 19/May/2010 2:25 PM

Will be working on 4.1 support very soon.

Cheers,
JC

JC added a comment - 19/May/2010 2:25 PM Will be working on 4.1 support very soon. Cheers, JC

Hans Menzi added a comment - 17/May/2010 12:10 PM

The exclusion of this functionality is preventing me from upgrading to the latest version of JIRA / GreenHopper.

Hans Menzi added a comment - 17/May/2010 12:10 PM The exclusion of this functionality is preventing me from upgrading to the latest version of JIRA / GreenHopper.

Aren Cambre added a comment - 17/May/2010 1:38 AM

This module is both unsupported and doesn't work on 4.1. Doesn't make sense that you depend on this for important functionality.

Aren Cambre added a comment - 17/May/2010 1:38 AM This module is both unsupported and doesn't work on 4.1. Doesn't make sense that you depend on this for important functionality.

G B added a comment - 11/Mar/2010 5:20 AM

My most-wished-for integration feature with the plugin is for there to be a clickable icon next to every issue link on every view issue screen that generates a Link Hierarchy Report for Issues for that issue using the link type matching the type of link that the clicked icon was next to.

G B added a comment - 11/Mar/2010 5:20 AM My most-wished-for integration feature with the plugin is for there to be a clickable icon next to every issue link on every view issue screen that generates a Link Hierarchy Report for Issues for that issue using the link type matching the type of link that the clicked icon was next to.

Nicholas Muldoon [Atlassian] added a comment - 13/Oct/2009 9:55 PM

Opportunities to integrate Links Hierarchy plugin into GreenHopper (via customer)

move the integration so that the card/summary/list view literally displays the hierarchy report
enhance cards/summary/list view with a modifier drop list to organize by which relationship (parent, depends, etc)
don't have report open in another window! Embed like other views using greenhopper

Nicholas Muldoon [Atlassian] added a comment - 13/Oct/2009 9:55 PM Opportunities to integrate Links Hierarchy plugin into GreenHopper (via customer) move the integration so that the card/summary/list view literally displays the hierarchy report enhance cards/summary/list view with a modifier drop list to organize by which relationship (parent, depends, etc) don't have report open in another window! Embed like other views using greenhopper

Jira Software Data Center

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

Collapse comment: Shaun Clowes (Inactive) added a comment - 26/Sep/2012 12:06 AM

Expand comment: Shaun Clowes (Inactive) added a comment - 26/Sep/2012 12:06 AM

Collapse comment: Mike Eldridge added a comment - 25/Sep/2012 8:44 PM

Expand comment: Mike Eldridge added a comment - 25/Sep/2012 8:44 PM

Collapse comment: Nicholas Muldoon [Atlassian] added a comment - 12/Jan/2012 10:41 PM

Expand comment: Nicholas Muldoon [Atlassian] added a comment - 12/Jan/2012 10:41 PM

Collapse comment: Steffen Stundzig [stundzig.it] added a comment - 12/Jan/2012 11:37 AM

Expand comment: Steffen Stundzig [stundzig.it] added a comment - 12/Jan/2012 11:37 AM

Collapse comment: Gary Murphy added a comment - 15/Dec/2011 5:53 PM

Expand comment: Gary Murphy added a comment - 15/Dec/2011 5:53 PM

Collapse comment: Chris Kent added a comment - 15/Nov/2011 12:53 AM

Expand comment: Chris Kent added a comment - 15/Nov/2011 12:53 AM

Collapse comment: Nancy Belser added a comment - 31/Oct/2011 1:47 PM

Expand comment: Nancy Belser added a comment - 31/Oct/2011 1:47 PM

Collapse comment: Nicholas Muldoon [Atlassian] added a comment - 29/Mar/2011 12:32 AM

Expand comment: Nicholas Muldoon [Atlassian] added a comment - 29/Mar/2011 12:32 AM

Collapse comment: Jim McCaskey added a comment - 13/Dec/2010 8:14 PM

Expand comment: Jim McCaskey added a comment - 13/Dec/2010 8:14 PM

Collapse comment: DaveT added a comment - 16/Nov/2010 9:35 PM

Expand comment: DaveT added a comment - 16/Nov/2010 9:35 PM

Collapse comment: Robert Sanders added a comment - 02/Nov/2010 9:09 PM

Expand comment: Robert Sanders added a comment - 02/Nov/2010 9:09 PM

Collapse comment: Ben Speakmon [Atlassian] added a comment - 06/Jul/2010 10:42 PM

Expand comment: Ben Speakmon [Atlassian] added a comment - 06/Jul/2010 10:42 PM

Collapse comment: Deleted Account (Inactive) added a comment - 28/Jun/2010 10:28 AM

Expand comment: Deleted Account (Inactive) added a comment - 28/Jun/2010 10:28 AM

Collapse comment: Nikolai Dokovski added a comment - 09/Jun/2010 7:33 AM

Expand comment: Nikolai Dokovski added a comment - 09/Jun/2010 7:33 AM

Collapse comment: JC added a comment - 08/Jun/2010 4:22 PM

Expand comment: JC added a comment - 08/Jun/2010 4:22 PM

Collapse comment: Hans Menzi added a comment - 08/Jun/2010 4:15 PM

Expand comment: Hans Menzi added a comment - 08/Jun/2010 4:15 PM

Collapse comment: JC added a comment - 08/Jun/2010 3:23 PM

Expand comment: JC added a comment - 08/Jun/2010 3:23 PM

Collapse comment: JC added a comment - 08/Jun/2010 3:02 PM

Expand comment: JC added a comment - 08/Jun/2010 3:02 PM

Collapse comment: Hans Menzi added a comment - 08/Jun/2010 2:57 PM

Expand comment: Hans Menzi added a comment - 08/Jun/2010 2:57 PM

Collapse comment: JC added a comment - 08/Jun/2010 1:46 PM, Edited by JC - 08/Jun/2010 1:47 PM

Expand comment: JC added a comment - 08/Jun/2010 1:46 PM, Edited by JC - 08/Jun/2010 1:47 PM

Collapse comment: Hans Menzi added a comment - 08/Jun/2010 1:40 PM

Expand comment: Hans Menzi added a comment - 08/Jun/2010 1:40 PM

Collapse comment: JC added a comment - 08/Jun/2010 1:29 PM, Edited by JC - 08/Jun/2010 1:57 PM

Expand comment: JC added a comment - 08/Jun/2010 1:29 PM, Edited by JC - 08/Jun/2010 1:57 PM

Collapse comment: Hans Menzi added a comment - 08/Jun/2010 1:00 PM

Expand comment: Hans Menzi added a comment - 08/Jun/2010 1:00 PM

Collapse comment: JC added a comment - 07/Jun/2010 5:04 AM, Edited by JC - 07/Jun/2010 5:07 AM

Expand comment: JC added a comment - 07/Jun/2010 5:04 AM, Edited by JC - 07/Jun/2010 5:07 AM

Collapse comment: JC added a comment - 02/Jun/2010 2:46 PM

Expand comment: JC added a comment - 02/Jun/2010 2:46 PM

Collapse comment: MattS added a comment - 02/Jun/2010 2:34 PM

Expand comment: MattS added a comment - 02/Jun/2010 2:34 PM

Collapse comment: MattS added a comment - 02/Jun/2010 2:26 PM, Edited by MattS - 02/Jun/2010 2:27 PM

Expand comment: MattS added a comment - 02/Jun/2010 2:26 PM, Edited by MattS - 02/Jun/2010 2:27 PM

Collapse comment: JC added a comment - 19/May/2010 2:25 PM

Expand comment: JC added a comment - 19/May/2010 2:25 PM

Collapse comment: Hans Menzi added a comment - 17/May/2010 12:10 PM

Expand comment: Hans Menzi added a comment - 17/May/2010 12:10 PM

Collapse comment: Aren Cambre added a comment - 17/May/2010 1:38 AM

Expand comment: Aren Cambre added a comment - 17/May/2010 1:38 AM

Collapse comment: G B added a comment - 11/Mar/2010 5:20 AM

Expand comment: G B added a comment - 11/Mar/2010 5:20 AM

Collapse comment: Nicholas Muldoon [Atlassian] added a comment - 13/Oct/2009 9:55 PM

Expand comment: Nicholas Muldoon [Atlassian] added a comment - 13/Oct/2009 9:55 PM

People

Dates

Backbone Issue Sync