| Age | Commit message (Collapse) | Author |
|
Used to check if target files have the expected hash. Using a
memory cache to not have to read source each time but falls back
to reading source if needed.
|
|
Can't create entries with "/" in for the other backends, so they
will resolve the path. documents would not. Change that so they
are more similar.
|
|
Had to fixup the symlink code in Sftp, most importantly add a PathUtils
relativeTo to fixup relative links.
|
|
There is no reason to use the Java version when there is the Kotlin version (for now).
|
|
Otherwise you get problems with one file system uses seconds and
another milliseconds and suddenly two files that are created at
the same time does not have the same timestamp.
Makes the test suite take 2 seconds longer to run but it is
what it is.
|
|
Will be easier to include in other projects then.
And it is where TreeAbstractTest is.
|
|
|
|
It's implementation specific if path is relative or absolute but
it contains the link target. Especially useful for NoTarget.
|
|
Fix implementations to work as expected
(that createDirectory/File/Link fails if an entry with that name
already exists).
|
|
And fix errors in MUTF-8 conversion in jni.cpp
|
|
sftp implementation using libssh2 and openssl
|
|
Reads the abomination that is SAF, or Androids best effort to make
files and directories completely and utterly unusable on Android.
The androidTest was (and is) a pain, only known to work on a
Pixel3 API 34 emulator but it showed a lot of things that the
fake content provider in the unit tests failed to show.
|
|
|
|
Will make it possible to use TreeAbstractTest in androidTest
as well as unittest
|
|
Most the tests test the Tree implementation and thus should work
on all such implementations. Current exception is symlinks which
Samba backend doesn't (currently?) support.
Improve the Samba remove methods to better match the expected behavior.
|