On Thu, Jun 12, 2008 at 2:46 AM, Ralph Goers <[EMAIL PROTECTED]> wrote: > I haven't been following this list all that long so I'm interested in > knowing why you want the package names changed. (I apologize in advance to > those who have already heard this before). >
Sure. We should probably have a wiki page for this topic (perhaps we do already?). Anyway, the idea is that if we change the package names to match the major release version number (so in this case, it'd be org.apache.commons.lang3.*), then we help avoid "jar hell." The Apache Commons projects are somewhat unique, in that they're used by a lot of other projects that, in turn, are used by "users". If Project X and Project Y both are very popular open source projects, and they depend on two different (and the key here is incompatible) versions of Commons Lang, then how do you set up your classpath to keep both projects happy if you want to use them? Well, if Project X codes to org.apache.commons.lang and Project Y codes to org.apache.commons.lang3, then there are no worries. Problem solved. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
