Cannot run bamboo/jira/confluence plugin if Licensing API module has been added

Description

Summary

Creating a bamboo plugin with a module will result in a fatal error during spin-up (atlas-run).

Steps to Reproduce

  1. Step 1
    atlas-create-bamboo-plugin

  2. Step 2
    Inside of new project: atlas-create-bamboo-plugin-module (added module type 4 in this instance - API License)

  3. Step 3
    atlas-run

Expected Results

Module installs to spun-up instance and deploys successfully to localhost.

Actual Results

The below exception is thrown in the xxxxxxx.log file:

Workaround

(If there is no workaround directly say so)
Currently no workaround - adding a License API plugin-module will break bamboo plugin.
Add the Licensing module using the instructions https://developer.atlassian.com/platform/marketplace/adding-licensing-support-to-server-apps/

Environment

None

Testing Notes

Can you create a new bamboo plugin, add module 4 and then run it successfully?

Activity

Show:
Joseph Harris
May 17, 2018, 6:34 AM

On replacing the above usage of component and component-import https://bitbucket.org/atlassian/atlassian-spring-scanner/src/master/ read from: Add scanner annotations to your code

Joseph Harris
May 17, 2018, 6:06 AM
Edited

Actually only dies when a (4) Module - API License is created... 2 other modules types built and ran successfully.

Adding the module inserts

Which is (now) forbidden use of component-import instead of spring scanner. Commenting it out allows the plugin to be run and installed.

Joseph Harris
April 11, 2018, 1:54 AM

This fatal occurs before can occur.

Fixed

Assignee

Ashwal Dixit

Reporter

Joseph Harris

Labels

Add-on Type

None

Team

None

CC

None

Risk factor

None

QA Kickoff Status

None

QA Demo Status

None

Story point estimate

None

Story Points

4

Sprint

None

Fix versions

Priority

Major