Hi @nickzhums, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions for Improving POM.xml Editing UX

Decouple XML extension dependency and recommend it for richer XML editing
• Users gain validation, IntelliSense and schema support from the XML extension
• See discussion in vscode-maven#47: Improve pom.xml editing experience vscode-maven#47 (comment)
Offer in-editor assistance for common POM tasks
• Auto-complete snippets for <dependency>, <plugin>, <property> elements
• Quick-pick UI to search/add Maven artifacts with version suggestions
Surface project build options directly in the editor
• Toggle auto-build or lifecycle phases without editing POM tags
• Reference: vscode-java-pack#883 on enabling/disabling auto-build Explore better Maven UX to enable/disable auto-build #883

Other references with low confidence

Improve outline UX (not POM-specific) — vscode-java-pack#875: Improve outline user experience to present more information #875
Project wizard enhancements — vscode-java-pack#881: Explore better project wizard mechanism #881

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

Brainstorm how we can provide better UX when editing POM (XML integration) #914

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions