I’ve installed the Ignition Module SDK, and am setting up for development using the Eclipse IDE. Before I get too deep into this, I would like to be sure I will be able to work efficiently in the long run.
Two functions that may be issues down the road, if I keep using Eclipse:
Using one specification for dependencies. Reading the Ant build file, and running the Eclipse app, I gradually realized that there are two builds going on: the Eclipse build and the Ant build. I have seen several people in the google-verse talk about problems keeping Eclipse and Ant on the same page with regard to dependencies. Apparently there is a way to use IVY for this purpose, but it seems better to have one software tool handling dependencies than three.
Using a version control system. I haven’t used any version control system in the past, but have often wished I had. So I’m going to set things up right this time. Eclipse supports CVS, and (as far as I can tell) only CVS. From the CVS web site I gather that it has not been updated since 2005. NetBeans supports several version control systems, including git, which I believe is up to date and widely used.
Whatever IDE I use, it must support remote debugging of the module as it runs in the gateway. It’s not clear to me at this point that NetBeans supports debugging code running in the Gateway, although it does say it supports remote debugging.
Anyone have any experience with NetBeans, or other alternate IDE?
Opinions about Eclipse relative to alternate IDEs?
Thanks for your help.