[MGNLIMG-202] Make module compatible with new publishing module Created: 13/Sep/17 Updated: 10/Oct/17 Resolved: 27/Sep/17 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.4 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Milan Divilek | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | Activation rewrite |
| Sprint: | Kromeriz 114, Kromeriz 115 |
| Story Points: | 1 |
| Description |
|
Module Magnolia Imaging Module (version 3.3.1) is dependent on activation (version 5.0/*), which was not found. Evaluate why dep to activation is there, remove it? |
| Comments |
| Comment by Philip Mundt [ 10/Oct/17 ] |
|
This was (also) integrated on 3.3.x (and not only like mentioned in fixVersion 3.4). Is this correct? If so do you mind updating the fixVersion? |