>>> * source compatibility for x.*.* >> >> Disagreed. I can quote numerous examples of application servers that >> come with varying versions of commons-foo, even within my employers >> house. Your proposal would mean that I had to create varying jar files >> of the applications shared library, depending on the application >> server.
Why are you using the jars from the app server would be my question. > We should not expect downstream users to change to a new binary API > (new package) more than (say) once a year, if that. IMO that's irrelevant as the users decide whether they upgrade or not. Never change a running system. If you do - well, stuff might break. Whoever is serious about avoiding jar hell inlines his dependencies anyway. (see maven shade plugin) cheers, Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
