garydgregory commented on pull request #26: URL: https://github.com/apache/commons-logging/pull/26#issuecomment-745339289
Well, I have no plans ATM to do so. But... if we release a new version that breaks binary compatibility, then we will have to change the package name and Maven coordinates, so that will be a source code change for call sites, which should/could be as simple as changing a package import from foo to foo2. Then, if we are going to bother going a major release, we should IMO break up this component into a multimodule project, which means that each module will be in its own package to make JPMS happy. If we did such a Maven modularization in 1.x while keeping the package names the same, then this would cause Java 9 and up to complain and maybe not even work since all the implementations are in the same package today. Any thoughts from you or the community? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
