> If they are still on Java 6 or 7, then updating libraries might not be a > priority. > > Gary
I second that. If an organization is still reluctant to upgrade at least to JDK 8, its rather unlikely that the same organization is urgently requiring to update to any latest commons release. And if they do in fact urgently require functionality, that is only available in a commons lib requiring JDK 8, it would be a nice incentive for finally considering an to upgrade at least to JDK 8. To me, Apache, especially commons, does a terrific job guarding BC, but in the end, trying to keep this up for the eternity will overstretch the communities resources, and it is breaking the stride. <RANT>On a more personal note: being 20+ years in the industry, I'm really fed up with organizations wanting me to build the newest, shiniest, fanciest crystal palaces of applications, while at the same time restricting me to use the tools from the stone age to achieve that, just because some oaf up there needs the money to upgrade the gadgets in his super yacht. You know, there is something wrong, when the model of the CEO's car is changing more frequently than the versions of your tools. Basically, an organization showing this behaviour is dumping their leniency as a debt into the community, so complaints about that shouldn't be taken too serious. </RANT> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
