-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
POM editor "Format" command is not available #1373
Comments
@mickaelistria can you take a look here? |
I cannot reproduce it with latest snapshots:
@JoMWal please try those snapshots from the various sources (it can be a bit of a maze to get them all at once, so feel free to ask if you feel stuck). |
Hi,
So I guess this issue can be closed. Thank you! |
Thank you for testing! |
Exactly this happens here again with: Linux 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux Operating System: Debian GNU/Linux 12 Eclipse IDE for Enterprise Java and Web Developers (includes Incubating components) Version: 2024-12 (4.34.0) Plug-in: |
Same issue: pom editor: format source not working #493. And another including it Pom.xml editor doesn't have all the features it previously did #458:
And a new one opened by me: POM Editor formatting doesn't work #1907. |
IDE: "Eclipse for RCP and RAP Developers" 2023-06
Newly installed by eclipse installer 2023-05-11) with clean workspace
Project: New (simple) Maven Project, type: pom
The pom.xml of the project is opened by default with the Maven POM editor.
But it is not possible to format the pom.xml.
Opening the same pom.xml file in default XML editor it is possible to format file:
o
I do not know if it's related but in the second screenshot there are two "source" entries in the eclipse menu bar.
--
Additional infos - Installed feature versions:
-- 1.0.4.202304211433 org.eclipse.wildwebdeveloper.xml
-- 0.16.0.202303141217 org.eclipse.lsp4e
-- 2.0.300.20230130-0743 org.eclipse.m2e.editor
-- 2.0.2.20230202-1631 org.eclipse.m2e.editor.lemminx
The text was updated successfully, but these errors were encountered: