[MAGNOLIA-6075] Follow java-free module conventions by default Created: 16/Feb/15 Updated: 17/Mar/15 Resolved: 10/Mar/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | configuration |
| Affects Version/s: | 5.4 |
| Fix Version/s: | 5.4 |
| Type: | Task | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | config | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Sprint: | 5.4 Sprint 1 | ||||||||||||||||
| Description |
|
Currently, config-by-file is bound to registries via the YamlConfigurationSourceBuilder, which requires each module having a registry to build such source, using sensible default for e.g. root path or file name regex pattern. As a first step, we have to follow java-free module conventions, i.e. /<module>/<definitionType>/<relativePath>/<name>.yaml, when we bind sources to registries with defaults. As a separate step ( |