Add comparison to Apache Commons Compress in README #391
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR addresses the issue where users found it difficult to understand what Plexus Archiver is and how it compares to Apache Commons Compress, especially why one should choose Plexus Archiver over Commons Compress.
Changes
Updated
README.md
to include:1. Introduction Section
Added a "What is Plexus Archiver?" section that clearly describes Plexus Archiver as a high-level Java API for creating and extracting archives with a simple, unified interface.
2. Comprehensive Comparison Section
Added a detailed "Comparison to Apache Commons Compress" section that explains:
3. Decision Guide
Added a "When to Use Which?" section with clear guidance:
Benefits
Fixes #[issue number]
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.