Jira Custom Plugin Can Not Enabled

[udogan]

Hi,

We are developing a Jira plugin which has dependency to Tempo plugin. We are usign Tempo plugin's methods and classes to make some calculations. We fallowed tutorials to create web-panel and etc. When we add dependency to Tempo plugin in pom.xml, our custom plugin enabled and worked without errors; but Tempo plugin started to get errors.

The error was:

[INFO] [talledLocalContainer] 2013-06-11 14:11:12,612 http-2990-5 ERROR admin 851x812x1 1waowtd 78.188.101.175 /secure/TempoInfo.jspa [jira.web.dispatcher.JiraWebworkActionDispatcher] Exception thrown from action 'TempoInfo', returning 404
[INFO] [talledLocalContainer] org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.tempoplugin.view.TempoInfoAction': Unsatisfied dependency expressed through constructor argument with index 0 of type [com.tempoplugin.TempoServiceFactory]: : No unique bean of type [com.tempoplugin.TempoServiceFactory] is defined: Unsatisfied dependency of type [class com.tempoplugin.TempoServiceFactory]: expected at least 1 matching bean; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.tempoplugin.TempoServiceFactory] is defined: Unsatisfied dependency of type [class com.tempoplugin.TempoServiceFactory]: expected at least 1 matching bean
...
...
[INFO] [talledLocalContainer] Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.tempoplugin.TempoServiceFactory] is defined: Unsatisfied dependency of type [class com.tempoplugin.TempoServiceFactory]: expected at least 1 matching bean

After searching the solution of the problem we saw a solution which was adding <component-import key="tempoServiceFactory" interface="com.tempoplugin.TempoComponent"/> to atlassian-plugin.xml.

After this addition another problem occurs. Our custom plugin can not enabled anymore.

The new error is:

[INFO] [talledLocalContainer] 2013-06-11 14:17:52,184 main ERROR      [plugin.osgi.factory.OsgiPlugin] Detected an error (BundleException) enabling the plugin 'com.kartaca.tempo' : Unresolved constraint in bundle com.kartaca.tempo [107]: Unable to resolve 107.0: missing requirement [107.0] package; (package=com.tempoplugin).  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
[INFO] [talledLocalContainer] 2013-06-11 14:17:52,186 main WARN      [plugin.osgi.factory.OsgiPlugin] Unable to enable plugin 'com.kartaca.tempo'
...
...
[INFO] [talledLocalContainer] Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.kartaca.tempo [107]: Unable to resolve 107.0: missing requirement [107.0] package; (package=com.tempoplugin)

Pom.xml:

<dependencies>
        <dependency>
            <groupId>com.atlassian.jira</groupId>
            <artifactId>jira-api</artifactId>
            <version>${jira.version}</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.10</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>com.atlassian.plugins</groupId>
            <artifactId>atlassian-plugins-osgi-testrunner</artifactId>
            <version>${plugin.testrunner.version}</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>javax.ws.rs</groupId>
            <artifactId>jsr311-api</artifactId>
            <version>1.1.1</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.mockito</groupId>
            <artifactId>mockito-all</artifactId>
            <version>1.8.5</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.ofbiz</groupId>
            <artifactId>ofbcore-share</artifactId>
            <version>2.1.1</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-context</artifactId>
            <version>2.5.6</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>com.tempoplugin</groupId>
            <artifactId>tempoplugin</artifactId>
            <version>7.6.0.1</version>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
            <version>2.4</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>com.atlassian.jira</groupId>
            <artifactId>jira-tests</artifactId>
            <version>${jira.version}</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>com.atlassian.jira</groupId>
            <artifactId>jira-core</artifactId>
            <version>${jira.version}</version>
            <classifier>classes</classifier>
            <scope>provided</scope>
        </dependency>
    </dependencies>
    <build>
        <plugins>
            <plugin>
                <groupId>com.atlassian.maven.plugins</groupId>
                <artifactId>maven-jira-plugin</artifactId>
                <version>${amps.version}</version>
                <extensions>true</extensions>
                <configuration>
                    <pluginArtifacts>
                        <pluginArtifact>
                            <groupId>com.atlassian.activeobjects</groupId>
                            <artifactId>activeobjects-plugin</artifactId>
                            <version>0.19.7</version>
                        </pluginArtifact>
                        <pluginArtifact>
                            <groupId>com.atlassian.activeobjects</groupId>
                            <artifactId>activeobjects-refapp-spi</artifactId>
                            <version>0.19.7</version>
                        </pluginArtifact>
                    </pluginArtifacts>
                    <productVersion>${jira.version}</productVersion>
                    <productDataVersion>${jira.version}</productDataVersion>
                    <log4jProperties>src/aps/log4j.properties</log4jProperties>
                </configuration>
            </plugin>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
        </plugins>
    </build>

[Alexej Geldt]

this happens not only with Tempo plugin. We have same annoying problems trying to have a plugin being dependent on another plugin. This mechanism seems to be broken.

[Benedikt Bjarni Bogason [Tempo]]

Hi, can I quickly enquire what problem you are trying to solve? Perhaps you can use our public API to solve this use case, or we might see value to add to our public API.

I *think* you can only import classes from the Tempo plugin that are explicitly exported in the Tempo pom.xml

Benedikt,

Tempo Team

[udogan]

We tried two approaches for our plugin in order to use tempo-plugin;

1. First we tried adding tempo-plugin to our plugin's pom.xml as a dependency. Tempo-plugin's classes were added to our WEB-INF/lib and our plugin worked fine and dandy in this case. But when we tried to enable the original tempo-plugin with UPM, somehow it didn't work. We got this error:

[INFO] [talledLocalContainer] Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.tempoplugin.TempoServiceFactory] is defined: Unsatisfied dependency of type [class com.tempoplugin.TempoServiceFactory]: expected at least 1 matching bean

I think probably there were some cache issues. Because essentialy we were using two of the same manager/service running.

2. Second thing we tried is to add tempo-plugin with import package and add tempo-plugin as a plugin dependency in our pom.xml and create an obr for our plugin. Obr was created alright and the original tempo plugin would run alongside. But then this time, we got this error in our plugin:

[INFO] [talledLocalContainer] java.lang.NoClassDefFoundError: com/atlassian/jira/plugin/webfragment/contextproviders/AbstractJiraContextProvider
[INFO] [talledLocalContainer] at java.lang.ClassLoader.defineClass1(Native Method)

(which is weird because AbstractJiraContextProvider is in jira-api and jira-api was added in our pom.xml as a dependency). We tried addding component-imports to atlassian-plugin.xml for the services we wanted to use in tempo-plugin. But according to tempo's atlassian-plugin.xml those services were not public, private by default. So component-import didn't work either.

We finally decided to use tempo's public API and rewrite our plugin in that direction. If you have any suggestion to overcome the problems we mentioned above that would be really helpful, so we wouldn't have to rewrite the whole thing.

[Benedikt Bjarni Bogason [Tempo]]

Hi,

Sorry for the late reply.

We have been conscientiously restricting access to our TempoServiceFactory class, as it is only meant for internal use by the plugin - it is a powerful beast, and you can wreak a lot of havoc by using it without knowing what you are doing. We have therefore considered it wiser to make that class private and instead offer a public API. We are very interested in hearing how other developers are using Tempo - and we would like to hear from you what we can do to make your job easier - such as what you feel is missing from our public API.

[Sverrir Tynes [Tempo]]

There are two system plugins that Tempo depends on, Tempo Core and Tempo Teams.

https://tempoplugin.jira.com/wiki/display/CORE/Tempo+Core+Home
https://tempoplugin.jira.com/wiki/display/TEAMS/Tempo+Teams+Home

Please verify that the system plugins jars are available in the installed-plugins directory.

Sverrir Tynes
Tempo support

[udogan]

Yes also we have
./jira/home/plugins/installed-plugins/tempo-teams-1.0.4.jar
./jira/home/plugins/installed-plugins/tempo-core-1.1.1.jar

[Jobin Kuruvilla [Adaptavist]]

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

Do you have the required Tempo version? You have 7.6.0.1 in the dependencies.


[udogan]

Yes, we have ./jira/home/plugins/installed-plugins/tempo-plugin-7.6.0.1.jar