garydgregory commented on PR #490: URL: https://github.com/apache/commons-compress/pull/490#issuecomment-1973251143
From my POV, if we do anything, and as a first cut, I would follow the route we are taking in Commons VFS: Move to new modules, format-specific code that is already in their own package that depend on a currently optional library, which is: brotli, zstd, and xz. There is no breakage of BC, just new artifacts. If you don't want to the artifacts, stick to the old one. Simple. For the implementation, the root POM needs to no longer generate a jar obviously so the current commons-compress artifact can move to a module dir and the root can be renamed commons-compress-parent. Having a BOM POM is nice and easy to add. Alternatively, the root POM can keep the same name, and the current code can move to a commons-conpress-core module. I think I like the first option better. -- 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]
