[MGNLMIGRATION-213] UpdateExtendsMigrationTask fails on relative paths Created: 14/Jan/13 Updated: 07/Feb/13 Resolved: 07/Feb/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | Migration Task |
| Affects Version/s: | 1.2 |
| Fix Version/s: | 1.2.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Ondrej Chytil | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Date of First Response: | |||||
| Description |
|
See linked support ticket for details. |
| Comments |
| Comment by Jan Haderka [ 07/Feb/13 ] |
|
the MigrationUtil.getAbsolutePath() method should return null if/when path can't be resolved and calling class should check result for null. If you return invalid path, later call to session.itemExists(invalidPath) will end up unnecessarily w/ exception. Also inside of the method when going up over ../ you should check whether you are not already on the root level and stop iterating and return null as a result since path is obviously invalid. |