Issue: Plugin Manager NullPointerException


When running the plugin-manager-cli file, you run into the following error:

Exception in thread "main" java.lang.NullPointerException
at com.xebialabs.plugin.manager.cli.PluginManagerCli.$anonfun$printPlugins$2(PluginManagerCli

at com.xebialabs.plugin.manager.cli.PluginManagerCli.$anonfun$printPlugins$2$adapted(PluginManagerCli

at scala.collection.immutable.List.exists(List.scala:395)
at com.xebialabs.plugin.manager.cli.PluginManagerCli.$anonfun$printPlugins$1(PluginManagerCli

at com.xebialabs.plugin.manager.cli.PluginManagerCli.$anonfun$printPlugins$1$adapted(PluginManagerCli

at scala.collection.immutable.List.foreach(List.scala:333)
at com.xebialabs.plugin.manager.cli.PluginManagerCli.printPlugins(PluginManagerCli.scala:96)
at com.xebialabs.xlrelease.PluginManagerCliBootstrapper$.runPluginManagerCli(PluginManager

at com.xebialabs.xlrelease.PluginManagerCliBootstrapper$.main(PluginManagerCliBootstrapper

at com.xebialabs.xlrelease.PluginManagerCliBootstrapper.main(PluginManagerCliBootstrapper.scala)

Root Cause

This issue is caused if any of the plugins doesn't follow the naming convention as per semantic versioning.

For example, test.jar instead of test-1.0.0.jar.


  1. Stop the application
  2. Delete the plugin from the directory (for example: rm release_home/plugins/__local__/test.jar)
  3. The run ./
  4. Once the plugin CLI loads, execute the following commands
    1. delete test
    2. delete any other plugins if needed
    3. Optional: run list to verify the plugin(s) has been deleted
    4. quit
  5. Proceed to fix the plugin's naming convention
  6. Lastly, you may place the newly renamed plugin(s) in the plugins/__local__ or upload them via the GUI when you start the application
Was this article helpful?
1 out of 1 found this helpful



Please sign in to leave a comment.