[MAGNOLIA-2271] Update/install is blocked if repository structure isn't standard Created: 16/Jul/08  Updated: 23/Jan/13  Resolved: 16/Jul/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.6 RC1
Fix Version/s: 3.6

Type: Bug Priority: Major
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MAGNOLIA-2274 CheckNodeTypesDefinition needs to wor... Closed
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

 Description   

the update task setup/for3_6/CheckNodeTypesDefinition.java is looking for a custom-nodetypes.xml file based on the repo home configuration property.
If the repositories.xml file has been customized and changed without using that property as the base path magnolia will never startup due to a FileNotFound exception. We should at least ignore it, making startup work as usual.



 Comments   
Comment by Fabrizio Giustina [ 16/Jul/08 ]

fixed with r16843, will merge on branch

Generated at Mon Feb 12 03:35:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.