sman-81 commented on PR #250: URL: https://github.com/apache/commons-csv/pull/250#issuecomment-1214729080
@kinow, @garydgregory Thanks for your good thoughts. > Don't forget that a major release entails a package name and artifact name change, [..] ``` org.apache.commons:commons-csv2 package org.apache.commons.csv2 org.apache.commons:commons-csv3 package org.apache.commons.csv3 ``` omg ... are you forced to do in this way by some set of conventions? I personally prefer semver and that changes to the major version are entitled to break binary compatibility. I don't know of anyone personally who replaces jars in a system without recompiling. I understand there is value in being able to do so (e.g. security patches). Does commons-csv or other Apache libraries publish and advertise this fact? It's kind of a unique feature, that comes at a price. If users don't know about the guaranteed binary compatibility, they would always recompile. I personally always recompile (working mostly on internal systems), as I would not want to take the risk of crashing with NoSuchMethodError at at run-time. The deprecation warnings will be addressed while removing old API and old tests in a new major release. We can close my PR - no problem at all. The work is easily recreated when releasing. Again, thanks for your thoughts and feedback - have a great week. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
