JIRA: Convert to plugin v2.

GoogleCodeExporter commented 9 years ago

The JIRA plugin is based on the v1 atlassian/jira plugin framework.

This means two things:

- upgrading the plugin requires manual work and a server restart.
- upgrading jira itself requires manual work to upgrade/reinstall the plugin.

Original issue reported on code.google.com by valentijnscholten on 9 Jan 2013 at 8:16

GoogleCodeExporter commented 9 years ago

BTW There's also a v3 plugin framework coming up.

Original comment by valentijnscholten on 9 Jan 2013 at 8:16

GoogleCodeExporter commented 9 years ago

yes, it may be great.

Can you provide a patch?
Source is here:
http://code.google.com/p/javamelody/source/browse/#svn%2Ftrunk%2Fjavamelody-core

The atlassian-plugin.xml file is here:
http://code.google.com/p/javamelody/source/browse/#svn%2Ftrunk%2Fjavamelody-core
%2Fsrc%2Fmain%2Fjira

It will need to work in Confluence, JIRA and Bamboo.

Original comment by evernat@free.fr on 9 Jan 2013 at 8:55

GoogleCodeExporter commented 9 years ago

I might if I have time somewhere in the future.

- Did you write any specific code for jira/confluence/bamboo, or only the 
atlassian-plugin.xml?
- Does javamelody support Tomcat7, because that's where JIRA is at atm.
- I don't have confluence and bamboo. If I make it work in JIRA, can you test 
the other two?

Original comment by valentijnscholten on 9 Jan 2013 at 9:02

GoogleCodeExporter commented 9 years ago

- Yes, but only this file:
http://code.google.com/p/javamelody/source/browse/trunk/javamelody-core/src/main
/java/net/bull/javamelody/JiraMonitoringFilter.java
- Yes
- Yes, I can test

Original comment by evernat@free.fr on 9 Jan 2013 at 9:34

GoogleCodeExporter commented 9 years ago

Original comment by evernat@free.fr on 28 Mar 2013 at 7:08

Added labels: Priority-Medium
Removed labels: Priority-High

GoogleCodeExporter commented 9 years ago

I can only help with bamboo. But I need a finished jar file plugin_v2. Because 
I don't understand java projects build system (using bamboo for C++ projects).

Original comment by alexey.ivanes@gmail.com on 5 Apr 2013 at 11:43

GoogleCodeExporter commented 9 years ago

I have tried to change the beginning of the atlassian-plugin.xml file inside 
the jar file of the plugin like this:

<atlassian-plugin key="net.bull.javamelody"
    name="JavaMelody Monitoring Plugin" pluginsVersion="2">
    <plugin-info>
        <description>Monitoring of JIRA, Confluence or Bamboo server with JavaMelody.</description>
        <version>1.44.0</version>
        <application-version min="4.0" />
        <vendor name="JavaMelody" url="http://javamelody.googlecode.com/" />
        <bundle-instructions>
            <Export-Package>net.bull.javamelody</Export-Package>
            <Import-Package>com.atlassian*,org.apache*,com.thoughtworks.xstream*,org.xmlpull*,*;resolution:=optional</Import-Package>
        </bundle-instructions>
    </plugin-info>
        ...

(pluginsVersion is changed and bundle-instructions is added).

But it does not work and jira says "BundleException: Unresolved constraint in 
bundle ... (package=com.atlassian)"

I certainly hate OSGI at this moment.

Original comment by evernat@free.fr on 19 Apr 2013 at 10:28

GoogleCodeExporter commented 9 years ago

Try to import com.atlassian.* instead of com.atlassian* (as well as the others).
BTW: the bundle-instructions usually belong into the pom.xml.

Create a licensing plugin (example) using the atlas-sdk, to see the setup für 
imported packages in both files.

Original comment by holle...@gmail.com on 21 Jun 2013 at 12:24

GoogleCodeExporter commented 9 years ago

The JavaMelody project has moved. Follow this issue at
https://github.com/javamelody/javamelody/issues/278

Original comment by evernat@free.fr on 12 Jul 2015 at 10:16

fengshao0907 / javamelody

JIRA: Convert to plugin v2. #278