[MGNLSTK-1000] Demo-project install task should check if Workflow module is installed Created: 14/Sep/12 Updated: 02/Jul/18 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | demoproject |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | 2.0.x |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
I followed Disabling activation workflow on a not-yet installed system. The instructions say I should remove magnolia-module-workflow.jar from the bundle and start installation. Installation failed at "Error while installing or updating demo-project module. Task 'Demo editors group' failed. (NullPointerException: )" If the Demo-project has a dependency on Workflow (why?) then the install task should check whether Workflow is installed. If no Workflow is installed then skip Demo-project installation and notify the user. |
| Comments |
| Comment by Jan Haderka [ 02/Jul/18 ] |
|
STK have been deprecated in September 2017. As part of this project nearing end-of-life, we are not planning to fix any of the existing issues except for the critical security issues. For more details, please consult documentation. |