Dependency on Marketplace plugins

I’m working on a plugin that depends on another plugin from the Marketplace, let’s say Portfolio.

Is there a way to put something in my plugin descriptor (pom.xml or atlassian-plugin.xml) to indicate the dependency?

What can I do to make the Jira instance started with AMPS (e.g. atlas-debug) start with my dependent plugin (Portfolio) installed?

1 Like

Konrad,

See pluginArtifacts here: https://developer.atlassian.com/server/framework/atlassian-sdk/amps-build-configuration-reference/

This example is also relevant and potentially helpful: https://bitbucket.org/bwoskow/optional-service-sample-plugin/src/master/

Scott

What if the plugin is not in a Maven repository that I can access?

If you don’t have your own Nexus server, you should still be able to install the other plugin locally to your ~/.m2/repository (“atlas-mvn install”) which would allow it to be picked up in your plugin’s pom.