Jme Sources

[neph1]

I'm still having trouble using the jMonkeyEngine sources in the sdk (3.5.x) If I open a source file, I get the "Generated code for.." I click "Attach sources..." I then get the option of selecting a zip, or download (which will "look up javadoc/sources in known Maven repositories") If I click "Download", it will download a huge maven index, which eventually fills up my HDD when unpacking. Is it perhaps a config issue?

Edit: Before downloading it says "No sources for xx:x available"

[peedeeboy]

Sadly, I don't think you are missing anything. This is the way vanilla NB works - it downloads the Maven central repository index, unzips it in your local cache directory, and then any Maven artefact searches (e.g. looking for source / javadoc artefacts, adding a library dependency via the UI...) are performed against the local index copy.

This was fine and dandy when NB's Maven support was first added (and was best in class!) as the Maven central repo was small, but now it is several GB both zipped and unpacked.

As NB unzips it into your user cache directory, when you download a new version of NB, it seems to go through that whole process again, and you end up with multiple copies of Maven index chewing up GB of space on your drive... always remember to delete your old NB cache directory when upgrading NB!

IIRC, some work was done to speed up the unzip process which I think was merged in. There was a proposal to remove the local indexing and always search Maven repos on-the-fly, but that was a couple of years ago and I don't think any work was done on it.

I think there was once a NB plugin to do this (switch to always searching Maven index online) - I had a look for it to see if it could be added to SDK by default, but doesn't seem to exist / be supported anymore.

[neph1]

I think it might be this one: https://github.com/emilianbold/maven.search.remote

[peedeeboy]

That's the badger - no idea if it still works with NB16 / solves the issue 🤷

[neph1]

Sadly not, it seems. The message "No sources for xx:x available" is displayed, but nothing happens.