Java development environments, or from Netbeans to Eclipse
In one of the largest state. of companies we conduct a small team of development of CAD on the Java platform
The project is already a year and a half.
Until recently, everyone used the Netbeans IDE together. Periodically enjoyed the new versions of the environment.
And now your humble servant saw the release of Netbeans 7.1. I wanted to try, see the novelty.
First I updated myself (Slackware Linux 12.2) . Launched, opened the project, compiled (compiled).
Everything went fine. He advised a colleague (Windows 7) , he continued to work in the new version.
Then the unimaginable began. Build the project went well, and when it is executed, a strange Exception-s. When clicking on Exception, Netbeans Editor opened an empty space in the code, where there was a comment at all, and not any method.
In this case, building the same project manually using Ant and then running from the command line gave an absolutely correct result.
It was concluded that Netbeans 7.1 runs some kind of private cache, and not just compiled Java classes!
The conclusion was confirmed, indeed, Netbeans has its cache in the user's home directory. But clearing it (deleting the .netbeans folder), as well as rebuilding the project multiple times, siphoning again from the version repository did not produce any results. Launching in the environment was still incorrect. The problem was solved only when the Netbeans project was created anew and all the sources were imported into it.
')
However, when it came to updating my environment with my colleague on Windows, such dances with the new version began anew, lasted another day and resulted in nothing. The project on Windows also started incorrectly, and giving out other errors in other places of the code.
In general, we decided to switch to Eclipse. While partly, the rest of the developers use Netbeans 7.0.1 for now.
The first days of development under 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 it passed, and apparently we will be transferring others to Eclipse as well, since work with the environment, giving unpredictable errors due to their own glitches - the enemy does not want.
But still sorry. What in my opinion Eclipse is inferior to Netbeans, is the intuitive interface.
In general, it is strange how this could happen with the proven Netbeans development environment!
The project is already a year and a half.
Until recently, everyone used the Netbeans IDE together. Periodically enjoyed the new versions of the environment.
And now your humble servant saw the release of Netbeans 7.1. I wanted to try, see the novelty.
First I updated myself (Slackware Linux 12.2) . Launched, opened the project, compiled (compiled).
Everything went fine. He advised a colleague (Windows 7) , he continued to work in the new version.
Then the unimaginable began. Build the project went well, and when it is executed, a strange Exception-s. When clicking on Exception, Netbeans Editor opened an empty space in the code, where there was a comment at all, and not any method.
In this case, building the same project manually using Ant and then running from the command line gave an absolutely correct result.
It was concluded that Netbeans 7.1 runs some kind of private cache, and not just compiled Java classes!
The conclusion was confirmed, indeed, Netbeans has its cache in the user's home directory. But clearing it (deleting the .netbeans folder), as well as rebuilding the project multiple times, siphoning again from the version repository did not produce any results. Launching in the environment was still incorrect. The problem was solved only when the Netbeans project was created anew and all the sources were imported into it.
')
However, when it came to updating my environment with my colleague on Windows, such dances with the new version began anew, lasted another day and resulted in nothing. The project on Windows also started incorrectly, and giving out other errors in other places of the code.
In general, we decided to switch to Eclipse. While partly, the rest of the developers use Netbeans 7.0.1 for now.
The first days of development under 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 it passed, and apparently we will be transferring others to Eclipse as well, since work with the environment, giving unpredictable errors due to their own glitches - the enemy does not want.
But still sorry. What in my opinion Eclipse is inferior to Netbeans, is the intuitive interface.
In general, it is strange how this could happen with the proven Netbeans development environment!
Source: https://habr.com/ru/post/140745/
All Articles