>>>>> I still think it should be renamed, but I think I lost that battle.
CSV is the name of the least surprise ...even if it supports e.g. TSV as well. I would keep the name just for user to find it. Especially as the line between CSV/TSV/TXT is quite blurry. > Since CSV is currently only a single package with very few classes, > would it perhaps be suitable as a part of an existing Commons > component? > > For example, Codec? I don't see that fit. It's small but no one will expect it in Codec. > Just a thought. > There are ways around the jar size if that is considered to be a > problem (e.g. Net releases its FTP code as a separate jar as well as > combined). Even if you want your artifact to be as small as possible - here are ways to do this. This is a packaging problem of the project not it's dependencies. cheers, Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
