Why not a new branch in the existing repo? Benedikt
Ralph Goers <ralph.go...@dslextreme.com> schrieb am Do. 16. März 2017 um 06:54: > Yes, and here we are with Java 9 at our doorstep. Time flies. > > I would recommend that you create a commons-vfs3 git repo for this as you > will only be able to borrow some code. A lot will be different. > > Ralph > > > On Mar 15, 2017, at 8:12 PM, Matt Sicker <boa...@gmail.com> wrote: > > > > Ralph has mentioned in the past an idea about rewriting commons-vfs using > > java.nio.file from Java 7. I was playing with this API today attempting > to > > abstract some S3 file operations using < > > https://github.com/Upplication/Amazon-S3-FileSystem-NIO2> and found that > > the API is pretty nice. OpenJDK already contains implementations for the > > normal file system and zip files if I recall correctly (so probably also > > jar files). > > > > Anyways, if we were to go forward with starting work on this, should we > > just make a commons-vfs3 branch in the vfs repo? Or does this belong in > the > > sandbox? > > > > -- > > Matt Sicker <boa...@gmail.com> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
