Java development environments, or from Netbeans to Eclipse

In one of the large state. A small team of companies has been developing CAD software on the Java platform. The
project has been a year and a half.
Until recently, everyone used the Netbeans IDE together . Periodically rejoiced to new versions of the environment.
And so your humble servant saw the release of Netbeans 7.1. I wanted to try, see the new product.
First updated myself (Slackware Linux 12.2) . Launched, opened the project, assembled (compiled).
Everything went fine. He advised a colleague (Windows 7) , he continued to work in the new version.

Then the unimaginable began. The project was built normally, and strange Exception-s appeared during its execution. When you clicked on Exception, the Netbeans editor opened an empty space in the code where there was generally a comment, and not some method.
At the same time, building the same project manually using Ant and then launching it from the command line gave an absolutely correct result.

It was concluded that Netbeans 7.1 runs some kind of native cache, and not just just compiled Java classes!

The conclusion was confirmed that Netbeans really has its cache in the user's home directory. But cleaning it up (deleting the .netbeans folder), as well as repeatedly rebuilding the project, pumping it out of the version store again did not give any result. The launch in the environment was still performed incorrectly. The problem was solved only when the Netbeans project was recreated and all the sources were imported into it.

However, when it came to updating my colleague’s environment on Windows, such dances with the new version started anew, continued for another day and did not lead to anything. The project on Windows also did not start correctly, and giving other errors in other places in the code.

In general, we decided to switch to Eclipse. Partially so far, the rest of the developers are still using Netbeans 7.0.1.

The first days of development for Eclipse Indigo left both good and bad impressions. I had to configure everything from scratch, create projects based on source codes, get used to another interface.
But this passed, and apparently we will also transfer others to Eclipse, because to work with an environment that gives unpredictable errors due to its own glitches - you will not wish the enemy.

But sorry. What Eclipse is inferior to Netbeans in my opinion is its intuitive interface.
In general, it’s strange how this could happen with the proven Netbeans development environment!

Also popular now: