Provide auto completion for bnd instructions in maven xml documents

[laeubi]

The bnd-maven and felix-bundle plugin provide a way to use bnd-instructions to build OSGi bundles. As this is a complex syntax that can not be expressed as regular maven-mojo configuration lemminx-maven can not supply any useful completions.

This adds a new lemminx-extension that provides such completions in a very basic way to support people writing such custom configuration.

Here is a little video showing the new completion support:

Peek.2024-11-15.17-45.mp4

@mickaelistria this shows how to deploy a lemminx-extension as a regular bundle inside m2e and providing additional jars to the flat-classpath using OSGi wiring API

[github-actions]

Test Results

  321 files  ±0    321 suites  ±0   53m 33s ⏱️ + 2m 29s
  678 tests ±0    659 ✅ +1  18 💤 ±0  0 ❌  - 1  1 🔥 ±0 
2 034 runs  ±0  1 979 ✅ +1  54 💤 ±0  0 ❌  - 1  1 🔥 ±0 

For more details on these errors, see this check.

Results for commit 10faeb6. ± Comparison against base commit 4074fc1.

♻️ This comment has been updated with latest results.

[laeubi]

This is currently quite basic and not super-smart, but will open up a whole bunch of new things to support, e.g. the next thing would be to add diagnostics to one can get errors, warnings and so on.

I therefore plan to merge this after the next m2e release for 2024-12 so we can further improve / experiment with that!

[mickaelistria]

@mickaelistria this shows how to deploy a lemminx-extension as a regular bundle inside m2e and providing additional jars to the flat-classpath using OSGi wiring API

That's really good, it does make things better. It's still not immune to libraries incompatibilities inside LemMinX process though, but that's another story.

[laeubi]

Yes it makes it just a little bit easier now from a deployment perspective as one does not need to collect everything manually. For more one would need to change how lemminx itself is launched, e.g if everything would be embedded inside the bundle (as with a very minimal example here) and only imports what is required to share the API then one could probably make it an connect-osgi-framework where each extension is its own bundle and encapsulates all requirements except the shared classes like lsp4j...