Hi Stephen!
Simple question - can [vfs] be released *now*, with a minimal set of
code?
I'd say, yes.
I presume that the first release might thus consist only of the core
plus standard java File and ram? No compress, ftp, http, ... I
emphasise, think small.
As Filip already pointed out, I too
I know, you said (as I do) the jar-per-filesystem is the clean solution
to go, but you also pointed out (as I do too ;-) ) the amount of work
for each voter then.
Sorry, but are you guys seriously saying that the work for each
voter is too much? In the end this means No, we cannot do 'release
Simple question - can [vfs] be released *now*, with a minimal set of code?
I presume that the first release might thus consist only of the core
plus standard java File and ram? No compress, ftp, http, ... I
emphasise, think small.
Subsequent releases could then add these features in, and
This is just my 0.02$ as a VFS user: I don't think such a minimal release is
very useful as the primary reason for using VFS is for using it for more
than
just a local FS. I think the suggest vfs/vfs-sandbox would work really well.
Cheers,
- Filip
Stephen Colebourne wrote:
Simple question -
On 7/27/06, Stephen Colebourne [EMAIL PROTECTED] wrote:
Simple question - can [vfs] be released *now*, with a minimal set of code?
I presume that the first release might thus consist only of the core
plus standard java File and ram? No compress, ftp, http, ... I
emphasise, think small.
On Fri, 2006-07-28 at 00:12 +0100, Stephen Colebourne wrote:
Simple question - can [vfs] be released *now*, with a minimal set of code?
I presume that the first release might thus consist only of the core
plus standard java File and ram? No compress, ftp, http, ... I
emphasise, think
Subsequent releases could then add these features in, and potentially
provide the split jar files (if someone, eg a maven expert, wants to set
up the multi jar solution)
With jci we already have multi module project in the sandbox. So that
might help with the setup.
cheers
--
Torsten
