[
https://issues.apache.org/jira/browse/IO-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondra Žižka updated IO-364:
---------------------------
Component/s: Utilities
Description:
{code}
handleFile( File file, int depth, Collection results )
{code}
and other methods provide a file object with full path.
As it's much easier to concat base path and additional path than "substracting"
one path from other, I suggest:
The `File` object provided by `handleFile()` and other `handle*` methods should
(optionally) contain path relative to the one passed to `walk()`.
was:
{code}
handleFile( File file, int depth, Collection results )
{code}
and other methods provide a file object with full path.
As it's much easier to concat base path and additional path than "substracting"
one path from other, I suggest:
The `File` object provided by `handleFile()` and other `handle*` methods should
contain path relative to the one passed to `walk()`.
Affects Version/s: 2.4
> Allow DirectoryWalker provide relative paths in handle*()
> ---------------------------------------------------------
>
> Key: IO-364
> URL: https://issues.apache.org/jira/browse/IO-364
> Project: Commons IO
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.4
> Reporter: Ondra Žižka
>
> {code}
> handleFile( File file, int depth, Collection results )
> {code}
> and other methods provide a file object with full path.
> As it's much easier to concat base path and additional path than
> "substracting" one path from other, I suggest:
> The `File` object provided by `handleFile()` and other `handle*` methods
> should (optionally) contain path relative to the one passed to `walk()`.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
