Remote development best practices
I'm getting back into Java development to finish up an odd project that has languished for too long. The problem I face is that I'm not sure how best to design my system as my requirements are a bit odd.
Simply put, I have a hardware device (a CD-ROM library) that I am going to control via JNI. However, I cannot develop locally on the attached machine and so I'm doing work on my laptop. Also, I want to be able to use JUnit as I'm a huge fan of unit-based testing. So this means that I need to be able to develop code locally (laptop) yet execute, debug, and version on the remote system (I'm using Subversion for the versioning).
Right now, I'm using NoMachine ( http://www.nomachine.com ) to work on the remote device, but it's just laggy enough to make the experience unpleasant. Since I use Eclipse, for my development environment, perhaps this question is more suited for the Eclipse forums, but I thought I'd try here first.
This seems like a similar problem to those encountered by people working on application servers, but I have no need for that amount of overhead (or do I?)
Any suggestions would be greatly appreciated!
(BTW: this Eclipse plugin, if compatible would be ideal: http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,8319,00.html )
