java.lang.IllegalArgumentException: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact

Atlassian JIRA | Brad Baker [Atlassian] | 7 years ago
  1. 0

    I created a directory in the <jirahome>/installed-plugins and it turns up as a broken plugin {code} bbaker@carltondraught:~/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins$ ls -l total 1572 drwxr-xr-x 10 bbaker bbaker 4096 2009-12-21 10:34 as {code} and then {code} 2009-12-21 10:37:16,171 main ERROR [atlassian.plugin.loaders.DirectoryPluginLoader] Unable to deploy plugin 'null', file Unit: jirahome/plugins/installed-plugins/as (1261352060000) java.lang.IllegalArgumentException: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact at com.atlassian.plugin.DefaultPluginArtifactFactory.create(DefaultPluginArtifactFactory.java:38) at com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:111) at com.atlassian.plugin.loaders.ScanningPluginLoader.loadAllPlugins(ScanningPluginLoader.java:88) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:135) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:210) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42) {code} and also it shows up on the plugins screen as an installed plugin - with the name being plugin name Its this really intended behaviour? Seems wrong to me. Also for the record the directory was an expansion of activity stream and hence was in fact a valid expanded jar. is it the intention of plugins to be able to read "expanded" jars as directories. if so then this is broken. {code} as Description: Vendor: (unknown) Plugin Version: 0.0 JIRA Version: 0.0 Installation Mode: Embedded There were errors loading this plugin: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact {code}

    Atlassian JIRA | 7 years ago | Brad Baker [Atlassian]
    java.lang.IllegalArgumentException: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact
  2. 0

    I created a directory in the <jirahome>/installed-plugins and it turns up as a broken plugin {code} bbaker@carltondraught:~/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins$ ls -l total 1572 drwxr-xr-x 10 bbaker bbaker 4096 2009-12-21 10:34 as {code} and then {code} 2009-12-21 10:37:16,171 main ERROR [atlassian.plugin.loaders.DirectoryPluginLoader] Unable to deploy plugin 'null', file Unit: jirahome/plugins/installed-plugins/as (1261352060000) java.lang.IllegalArgumentException: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact at com.atlassian.plugin.DefaultPluginArtifactFactory.create(DefaultPluginArtifactFactory.java:38) at com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:111) at com.atlassian.plugin.loaders.ScanningPluginLoader.loadAllPlugins(ScanningPluginLoader.java:88) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:135) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:210) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42) {code} and also it shows up on the plugins screen as an installed plugin - with the name being plugin name Its this really intended behaviour? Seems wrong to me. Also for the record the directory was an expansion of activity stream and hence was in fact a valid expanded jar. is it the intention of plugins to be able to read "expanded" jars as directories. if so then this is broken. {code} as Description: Vendor: (unknown) Plugin Version: 0.0 JIRA Version: 0.0 Installation Mode: Embedded There were errors loading this plugin: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact {code}

    Atlassian JIRA | 7 years ago | Brad Baker [Atlassian]
    java.lang.IllegalArgumentException: The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact
  3. 0

    [JRA-19401] JIRA 4.0 does not run in Websphere 7.0 - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplu gin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifes t header
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JRA-19980] JIRA v4.0.1 does not start on WebSphere v7.0: The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symb name... - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header
  6. 0

    [JRA-20451] Jira Standalone does not work with IBM JVM 1.6 - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      The artifact URI file:/home/bbaker/src/atlassian/releases/jira4.0/jirahome/plugins/installed-plugins/as/ is not a valid plugin artifact

      at com.atlassian.plugin.DefaultPluginArtifactFactory.create()
    2. com.atlassian.plugin
      DefaultPluginManager.init
      1. com.atlassian.plugin.DefaultPluginArtifactFactory.create(DefaultPluginArtifactFactory.java:38)
      2. com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:111)
      3. com.atlassian.plugin.loaders.ScanningPluginLoader.loadAllPlugins(ScanningPluginLoader.java:88)
      4. com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:135)
      4 frames
    3. com.atlassian.jira
      ConsistencyLauncher.contextInitialized
      1. com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49)
      2. com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275)
      3. com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224)
      4. com.atlassian.jira.ComponentManager.start(ComponentManager.java:210)
      5. com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63)
      6. com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
      6 frames