Hi Vincent! > No but you could ask them to do a timestamped version. > Not sure if this fits the needs in commons to allow a release.
>> e.g. 10 vfs jars to get what you have now might become a pain. >> > It really depends. You have different types of users. Some will only want 2 > or 3 filesystem providers and they may not like that to have to download the > other 30 providers. > I understand. I also see its mavens philosophy, and AFAIK OSGi. You also say, in cargo you provide a single jar and individual jars. Unhappily, this wont work in VFS if we cant release one of the individual jars due to the outlined problems. I perfectly understand that VFSs filesystem implementations fits perfectly in such a scheme, to say the truth, for now I think its just way too much work for me. Not to separate the code, this might not be that hard, but to maintain them and its different releases. Once VFSs again has a significant number of developers we can go that way. Having the two-jar solution is a good compromise for now, no? Lets see what the other devs think about it. > I'm not prepared to sustain that level of emails (I already have too much) > so I'll be following sporadically from nabble. > No problem, I'll keep you informed. Ciao, Mario --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
