[MGNLDATA-265] Installing data module's company sample on java 8 gives corrupted subapps order Created: 20/Nov/14 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | content-app, java8 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Description |
|
1. Given that bootstrap files for the company-app sample are split "per subapp";
2. Given that JCR bootstrap files are not guaranteed to be processed in any particular order. 3. And given that the default subapp in apps when clicking the tile in the applauncher is always the first one — regardless of type or name; => When installing Magnolia on Java 8, the order bootstraps files are processed is different from Java 6, and thus the company detail subapp ends up being the first one. Consequently, opening the app from the applauncher opens an empty detail subapp, rather than the browser subapp. We may equally add an extra install task to order the browser subapp first, or aggregate all sample bootstraps into one. |