Version 1 to Version 2 causes problem with respect to conflicts due to different versions of components

 The following problems did not existed till my plugin was version 1. they
arised when i changed the version as plugin 2.

Problem 1

C:\myworkspace\myplugins\jira-odyssey-overdue-plugins\src\main\resources
2012-07-02 17:20:17,344 main ERROR      [plugin.osgi.factory.OsgiPlugin]
Detected an error (BundleException) enabling the plugin
'com.atlassian.labs.fastdev-plugin' : Unresolved constraint in bundle
com.atlassian.labs.fastdev-plugin [47]: package;
(&(package=com.atlassian.plugins.rest.common.security)(version>=2.4.0)). 
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
2012-07-02 17:20:17,392 main WARN      [plugin.osgi.factory.OsgiPlugin]
Unable to enable plugin 'com.atlassian.labs.fastdev-plugin'
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start
plugin: com.atlassian.labs.fastdev-plugin
    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:644)
    at
com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:153)
    at
com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:52)
    at
com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1326)
    at
com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:227)
    at com.atlassian.jira.ComponentManager.start(ComponentManager.java:212)
    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.atlassian.labs.fastdev-plugin [47]: package;
(&(package=com.atlassian.plugins.rest.common.security)(version>=2.4.0))

 

To fix this 1st problem I have used the following solution. I dont know if
it supresses the error or its a real fix.....

 <plugin>
                <groupId>com.atlassian.maven.plugins</groupId>
                <artifactId>maven-jira-plugin</artifactId>
                <version>3.7.2</version>
                <extensions>true</extensions>
                <configuration>
                    <enableFastdev>false</enableFastdev>
                    <productVersion>${jira.version}</productVersion>
                   
<productDataVersion>${jira.data.version}</productDataVersion>
                </configuration>
            </plugin>

 

Problem 2

OverdueIssuesTabPanel extends AbstractFragmentBasedProjectTabPanel which
internally implements ProjectTabPanel. The following error never existed
when the plugin was version 1 and was deployed in web-inf/lib. but it
existed when I changed the verion of the plugin to 2. I am not able to
understand what is causing this.....

2012-07-02 17:20:17,816 main ERROR     
[atlassian.plugin.manager.DefaultPluginManager] There was an error loading
the descriptor 'my.projectpanels.issues.name' of plugin
'jira-odyssey-overdue-plugins.jira-odyssey-overdue-plugins'. Disabling.
com.atlassian.plugin.PluginParseException: Given module class:
com.atlassian.jira.plugin.projectpanel.impl.OverdueIssuesTabPanel does not
implement com.atlassian.jira.plugin.projectpanel.ProjectTabPanel
    at
com.atlassian.plugin.descriptors.AbstractModuleDescriptor.assertModuleClassImplements(AbstractModuleDescriptor.java:307)
    at
com.atlassian.jira.plugin.projectpanel.ProjectTabPanelModuleDescriptor.assertModuleClass(ProjectTabPanelModuleDescriptor.java:27)

-- 
View this message in context: http://old.nabble.com/Version-1-to-Version-2-causes-problem-with-respect-to-conflicts-due-to-different-versions-of-components-tp34132698p34132698.html
Sent from the JIRA - User mailing list archive at Nabble.com.

_______________________________________________
Jira-user mailing list
[email protected]
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user