Task 2.2: Migrate JSoup Dependency
Open
Nobody has claimed this yet.
Team : Platform
Type : Task
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Task Description
Replace dot.jsoup with standard org.jsoup:jsoup dependency
Status: 🔄 PENDING
Scope
- Update 6+ import statements from repackaged JSoup to standard
- Remove
dot.jsoupfrom POM files - Add standard
org.jsoup:jsoupdependency to BOM - Test HTML parsing functionality
Implementation Plan
-
Dependency Update:
- Remove
com.dotcms.lib:dot.jsoupfrom BOM and dotCMS POM - Add standard
org.jsoup:jsoupto BOM with appropriate version - Update dotCMS POM to use standard dependency
- Remove
-
Code Migration:
- Find all imports:
com.dotcms.repackage.org.jsoup.* - Replace with:
org.jsoup.* - Update approximately 6+ import statements
- Find all imports:
-
Testing:
- Test HTML parsing functionality
- Verify content processing works correctly
- Run related unit tests
Acceptance Criteria
- [ ] All JSoup imports updated from repackaged to standard
- [ ] Standard JSoup dependency added to BOM
- [ ] Repackaged JSoup dependency removed from POM files
- [ ] All HTML parsing tests pass
- [ ] No functional regressions in HTML processing
- [ ] Integration tests pass
Claude Assistance Benefits
- Import Updates: Claude can handle bulk import statement changes across multiple files
- Pattern Recognition: Identify all JSoup usage patterns in codebase
- Testing Support: Help identify test cases that need verification
- Risk Assessment: Evaluate potential impact of JSoup version changes
Related
- Epic: #32675 - Remove Repackaged Dependencies
- Phase: 2 - Low-Risk Migrations
- Priority: Medium
- Estimated Effort: 1 day (with Claude assistance)
Technical Notes
- JSoup is used for HTML parsing and manipulation
- Verify version compatibility with existing code
- Check for any custom JSoup extensions or patches
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the BOM and dotCMS POM files, then search for com.dotcms.repackage.org.jsoup imports and the dot.jsoup dependency. Review the existing JSoup version and related unit or integration tests before making the migration. Done means standard imports and org.jsoup:jsoup are used, the repackaged dependency is removed, and HTML parsing and integration tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100