Changing the netbeans_default_cachedir in nf did not resolve the issue. The error message I received from NetBeans was misleading, because it claimed I did not have enough space in my ~/.cache/netbeans dir to perform the cacheing. Specifying a new location on a larger disk resolved the problem. On my machine, this indexing operation used almost 6GB of space, which was larger than I had available at the default java.io.tmpdir location. When opening a Maven POM for the first time, NetBeans will pull a file from Maven Central and index it, using the tmp dir. To fix, I modified the netbeans/etc/nf to specify a new tmp dir location in the netbeans_default_options setting, adding: -J-Djava.io.tmpdir=/my/new/tmpdir The root of the problem was that I was running out of disk space on my main drive (default tmp dir location). I recently ran into this problem on CentOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |