Closed GoogleCodeExporter closed 9 years ago
I have reproduced the issue with JIRA5 and the "javamelody monitoring plugin"
for JIRA.
This web-item comes from:
http://code.google.com/p/javamelody/source/browse/trunk/javamelody-core/src/main
/jira/atlassian-plugin.xml#55
It says:
<web-item key="net.bull.javamelody.jira-web-item" name="Monitoring"
section="system.admin/system" i18n-name-key="net.bull.javamelody.web-item"
weight="10">
<icon height="16" width="16">
<link>/monitoring?resource=systemmonitor.png</link>
</icon>
<label key="net.bull.javamelody.label">Monitoring</label>
<link linkId="net.bull.javamelody.link">/monitoring</link>
</web-item>
Do you know what should be changed in this web-item to fix the issue?
Original comment by evernat@free.fr
on 6 May 2012 at 12:44
I have finally found that the icon element in jira-web-item of
atlassian-plugin.xml is currently a problem for JIRA (tested on JIRA v5).
Indeed there is an error log when some pages are displayed, such as the project
config page.
So I have removed this icon element to fix the issue.
This is committed in trunk (revision 2797) and ready for the next release
(1.38).
I have made a new build of the plugin and it is available at:
http://javamelody.googlecode.com/files/jira-javamelody-20120506.jar
Original comment by evernat@free.fr
on 6 May 2012 at 3:18
I have the same problem with jira-javamelody-1.52.0.jar and JIRA6.2.7.
My solution was to replace the web-item section in atlassian-plugin.xml
with:
section="admin_plugins_menu/monitoring_section"
Now the error is gone and the monitoring page is in the right panel-section!
Original comment by olaf.k...@gmail.com
on 25 Aug 2014 at 6:13
Yes, the error log has appeared again in "recent" JIRA versions, as said in
issue 342 and https://jira.atlassian.com/browse/JRA-34147.
It's sad that Atlassian does not keep synonyms for previous locations and so
backward compatibility for plugins targeting several JIRA versions.
Star issue 342 to be notified of changes.
Original comment by evernat@free.fr
on 31 Aug 2014 at 1:51
Original issue reported on code.google.com by
devu.h...@gmail.com
on 21 Apr 2012 at 7:51