FileChunkManager manages mappings from paths to chunks
Tests for FileChunk's fail safe behavior
Changing which Closeable -> Flushable
More tests for FileChunkManager
FileChunkManager uses a URI (which will be passed in via a
FileSystemProvider) a default scheme of file is assumed, so
our:/path/to/metadata?scheme=file
is equivalent to
our:/path/to/metadata
Converted back to FileChunkManager only taking a path. The URI
conversion will be handled by the OuranosPath
Basic implementation of FileSystemProvider, FileSystem, and Path. The
URI scheme appends path information to the fragment and uses the query
portion to keep track of which scheme the metadata file is.
FileChunkManager -> FileSystemMetadata. It now uses JAXB for
serialization.
Eclipse was complaining about API compatiblity with 1.6.
http://stackoverflow.com/q/23362108/758280
Optimized save a little bit
Changed name
Apparently 1.5 doesn't work either. I guess Eclipse will just have to
complain
Namespace for the scheme is the hosting of this project. Added schema
generation to Maven
We're not using the generated schema anyways
Smarter null-value for JAXB initialization
Implemented some of the easier FileSystemProvider methods
Implemented checkAccess which is fairly important for File.exists
Fix tests
Fully implemented atomicMove. Half implemented copy
Rewrote FileSystemMetadata to be more useful. Instead of dealing with
primitive longs, it deals with Paths. To help facilitate the XML
conversion, I created model classes which somewhat mirror the structure
of Metadata and File, but in a format more suited for JAXB marshalling.
Moved tests away from complicated mock FileSystems and I'm instead
spying on a FileSystem which is based off of a temp directory.