[QAARQ-20] Remove personalization dependency Created: 27/Dec/17 Updated: 03/Sep/18 Resolved: 03/Sep/18 |
|
| Status: | Closed |
| Project: | Queued Asynchronous Activation over RabbitMQ |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Karel de Witte |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Description |
|
I would suggest a similar approach to what we do with blossom. If you use blossom and personalization together then you need to install an additional module. So here you can break out the code that depends on personalization into another RMQ module. |
| Comments |
| Comment by Richard Gange [ 03/Sep/18 ] |
|
Dependency has been removed. |