Difference between revisions of "NetBeans"
(better example of sshfs) |
(Adds troubleshooting info) |
||
| Line 11: | Line 11: | ||
<source lang="bash"> | <source lang="bash"> | ||
sudo sshfs -o IdentityFile=/home/greg/.ssh/id_rsa -o allow_other greg@eqt:/var/www/freephile.com/www/wikireport /mnt/droplet | sudo sshfs -o IdentityFile=/home/greg/.ssh/id_rsa -o allow_other greg@eqt:/var/www/freephile.com/www/wikireport /mnt/droplet | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</source> | </source> | ||
Revision as of 11:35, 17 March 2016
NetBeans is a really decent editor, but it lacks one important feature (who knows why?). If you ever wanted to work on a remote server without having to download files and/or synchronize them (which NetBeans is horrible at), then use this simple hack:
Use a remote filesystem available in your Operating System
e.g.
sudo sshfs -o IdentityFile=/home/greg/.ssh/id_rsa -o allow_other greg@eqt:/var/www/freephile.com/www/wikireport /mnt/droplet
Then, setup a project in NetBeans with existing sources, and use the mountpoint
Troubleshooting[edit | edit source]
See the process page for info on using the ps command to find out about your NetBeans process.
ps will tell you things about the various options (like Heap Size) that can be passed to the program on the command line, or set in defaults. For defaults, look at /etc/netbeans.conf Then, depending on your installation directory, look at the contents of the log file - which you can find using locate messages.log
Slow Startup (NetBeans background scanning projects takes too long)[edit | edit source]
When I tailed the messages.log file, I found out that the indexing took over 40 minutes. So, startup did actually finish as I spent an hour trying to figure out why it was taking so long.
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete indexing of 11 source roots took: 2,443,238 ms (New or modified files: 11,926, Deleted files: 2,371) [Adding listeners took: 23 ms]
