Posts

Showing posts with the label Eclipse

2014 July, Eclipse Development Survey Analyzed

Eclipse community have just released their yearly survey (about 900 participants). I see this survey as a good source of data to feel the current development vibe. Here is the Eclipse Survey So, I looked at the survey results several times and decided to write my specific conclusions extracted from the survey. I have analyzed the survey and want to only write about the big changes I saw which are worthy of my attention (and probably yours too if you read my post). My Personal Survey Conclusions Open source has lost some of it's prestige (a pity)  [Slide 9] Open Hardware and Internet of Things are here to stay [Slide 13, 17] Most Eclipse users, upgrade their IDE soon after each yearly release [Slide 15] Javascript is here to stay [Slide 21] Application Servers: Tomcat remains first, but JBoss is gaining [Slide 23] Repositories: CVS is finally dead, SVN is dying fast and GIT is gaining fast [Slide 24] Build Tools: Ant is dying fast, Maven is leading ...

Eclipse Window Builder VS Netbeans GUI Builder (Matisse)

Java is a great programming language but it has a big flaw - it's GUI framework sucks! I am talking about building simple client-side applications. If you don't want to mess with any web gui framework then you are bound to use swing. You can always build swing writing the text and imagining how it will work but any smart programmer will search for a nice Swing GUI builder which will enable him/her to have a WYSIWYG sort of framework to work with. There are several options of WYSIWYG frameworks to pick from, the most noticeable till the July (2011) was Netbeans' "Matisse" GUI builder. There were others of course but none as free or as good as Matisse. The biggest flaw of Matisse is that it doesn't reside on the best IDE out there - eclipse, but it can be found only on netbeans which isn't as good as Eclipse (Doesn't even have a "hover" feature to name one great flaw of netbeans) so if you want to build a GUI suppo...

Setting up an Android development environment in a nutshell

If you want to begin developing for the android platform - which components will you need to install? In a nutshell: Install latest JDK http://www.oracle.com/technetwork/java/javase/downloads/index.html Install the latest eclipse IDE "Eclipse IDE for Java Developers" http://www.eclipse.org/downloads/ Install the latest Android SDK http://developer.android.com/sdk/index.html Run the SDK manager after installation and install all of the packages you might need (retain default packages and add additional ones if need be). Install latest ADT (eclipse android plugin) Run eclipse, choose help --> Install new software https://dl-ssl.google.com/android/eclipse/ Configure eclipse and point it to the JDK and to the android SDK. Have a nice android day   :-) Avi.

Do you wish you could debug with your local Eclipse a Java program running on an other machine ... remotely?

Remote Debugging The General debug flow. In order to debug with your Eclipse a Java program that runs on an other machine, you will need to configure two components, one in the remote machine (Where the Java program runs) and the second is a local configuration addition to your Eclipse IDE. The Remote machine will run the Java program using a special command line argument which will tell the JVM that an external debugger will connect to it and how it will connect to it (Connection type, Port etc). The Local Machine which runs Eclipse should use a special debugging mode, configured to connect to the remote Java program. The Explicit configurations. Configuring the Remote Java program. When running the program just add these command line arguments after the "java" command before the "-jar" argument (For more detailed information about these arguments - read the article which it's link is attached below): -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,suspend=n...