One more thing: if you change the artifact ID, you need to change the Java package too. Publishing the same fully qualified class names under new maven coordinates is a deal breaker. It will cause very hard to diagnose and debug problems for many developers, including those who don't directly depend on commons-compress but just have somewhere deep in their transitive dependency tree.
https://jlbp.dev/JLBP-6 On Wed, Oct 8, 2025 at 12:17 PM Vladimir Sitnikov <[email protected]> wrote: > > Thanks, Gary, for the heads-up on 1.29 (fixes) and 1.30 (LHA). > > What do you think of moving LHA to its own module from day zero? > > In other words, what do you think of > * commons-compress-core (current core code, no behavior change) > * commons-compress-lha (new LHA code only) > * commons-compress meta POM that depends on both (preserves today’s > behavior; no shaded jar) > > I don't see the full picture, however, it looks like moving LHA to its own > module should not impact release timelines much. > > Vladimir -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
