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
