POM-Parsing inkonsistent: Regex in ProjectInfoTools vs. DOM in ProjectImporter #67
Labels
No labels
bug
build
enhancement
headless
P1-critical
P2-high
P3-medium
P4-low
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-tools/jdt-mcp-server#67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
ProjectInfoTools.parseMavenInfo()(Zeile 148ff) parstpom.xmlmit regulären Ausdrücken.ProjectImporterverwendet korrektDocumentBuilderFactorymit DOM-Parsing.Regex auf XML ist notorisch fehleranfällig (XML-Kommentare, CDATA-Sections, ungewöhnliches Whitespace).
Fix
ProjectInfoToolsauf den gleichen DOM-Parser umstellen. Idealerweise gemeinsam mit #56 (ProjectImporter-Aufteilung) einePomParser-Utility extrahieren.Gefunden von
Starke, Fowler