fix: update mason API usage for nvim-java compatibility

[Kabil777]

Summary

This PR updates deprecated Mason APIs (get_install_path) used in nvim-java-core to work with Mason v2.2.0+.

Changes

• Updated: init.lua in ls/servers/jdtls to use vim.fn.expand("$MASON/…") for finding JDK paths.
• Updated: utils/mason.lua to replace deprecated Mason API calls with standard path functions (vim.fn.stdpath).
• Handled: safe usage of get_package with pcall to avoid crashes when packages are not installed.

Motivation

Recent versions of mason.nvim removed or changed the get_install_path() method, breaking integration with nvim-java. This patch restores compatibility.

Testing

Tested with:

• Mason v2.2.0

---

[gierdo]

this error is so stupid and i need java because im training for usaco

You can install mason in version 1.x, or alternatively use nvim-java-compatibility from Kabil777's fork.

How you can do that depends on you plugin manager and your configuration, though. So it's a bit hard to guide you.

With lazy, e.g., you can do

  {
    "williamboman/mason.nvim",
    branch = "v1.x",
...

Or you can apply the fix proposed here:

LazyVim/LazyVim#6053 (comment)

Or you can do this:

  {
    "nvim-java/nvim-java",
...
    dependencies = {
      {
        "nvim-java/nvim-java-core",
        url = "https://github.com/Kabil777/nvim-java-core.git",
        branch = "fix/mason-api-update",
      },
    },
  },

[Zeioth]

@s1n7ax merging this PR is also necessary.

[s1n7ax]

this error is so stupid and i need java because im training for usaco

@Coding4Hours I don't give a shit wtf you are training for. Don't know how branches work? Then stop trying you will be replaced by AI in few months anyway

[s1n7ax]

In prev you used $MASON variable but here get stdpath?

[s1n7ax]

Can't we use $MASON env variable?

[s1n7ax]

Release notes states that the way to get the path is using $MASON environment variable. You could fix all occurrences to use $MASON or I fix and merge in few days. Formatting has to be fixed as well

[ahakanbaba]

Thank you very much for the hard work here. If I may ask, what would it take to push this PR through. It would be great to unblock the mason backward compatibility problem.

[s1n7ax]

@ahakanbaba The last time I accepted a mason 2.0 compatibility PR, it was broken on mason 1.0 as well as on mason 2.0. Now that I have some time to think about it, the changes should think about backward compatibility as well. I think I should do this myself but at the same time I don't have much time. too busy with personal stuff.