Split off the SQS queuing service to an external package

Issue #61 resolved

Jaiden Ashmore created an issue 2016-12-13

This is because I have other connect add-on that needs to be able to communicate with SQS so is to simplify this.

It is currently being split off so I just need to make it use this and delete the current implementation in this project.

Comments (8)

Jaiden Ashmore Account Deactivated reporter
refs ~~#61~~: Delete the old sqs queue from the project and moved it to a separate package

→ <<cset 449b35b4928e>>
- 2016-12-13T08:27:01+00:00
Jaiden Ashmore Account Deactivated reporter
refs ~~#61~~: Fix unit tests

→ <<cset b3599bed5aa2>>
- 2016-12-15T04:17:00+00:00
Jaiden Ashmore Account Deactivated reporter
refs ~~#61~~: Removed attempts to get the atlassian private repository working

→ <<cset acd785cd594f>>
- 2016-12-30T03:56:24+00:00
Jaiden Ashmore Account Deactivated reporter
- changed milestone to internal-release
- edited description
- 2017-02-02T07:04:10+00:00
Jaiden Ashmore Account Deactivated reporter
refs ~~#61~~: Delete the old sqs queue from the project and moved it to a separate package

→ <<cset 449b35b4928e>>
- 2017-02-11T02:09:51+00:00
Jaiden Ashmore Account Deactivated reporter
refs ~~#61~~: Fix unit tests

→ <<cset b3599bed5aa2>>
- 2017-02-11T02:09:51+00:00
Jaiden Ashmore Account Deactivated reporter
refs ~~#61~~: Removed attempts to get the atlassian private repository working

→ <<cset acd785cd594f>>
- 2017-02-11T02:09:52+00:00
Jaiden Ashmore Account Deactivated reporter
- changed status to resolved
- 2017-02-12T01:28:29+00:00
Log in to comment