[MAGNOLIA-8155] Resource mapping conflict is not detected Created: 27/Sep/17 Updated: 05/Apr/22 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | blocked, maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||
| Description |
|
We having a URI mapping for the resources workspace that is not being picked up. Most likely because of the custom mapping class used. Consider to remove most of the mappings. It should be sufficient to just leave the website mapping there, remove others. |
| Comments |
| Comment by Jan Haderka [ 19/Dec/17 ] |
|
please provide said custom mapping to reproduce issue. |