Development environment for Java, or Netbeans to Eclipse
In one of the largest state companies keep a small team developing CAD software for the Java platform
The project is already a year and a half.
Until recently, all together used Netbeans IDE. Periodically rejoiced new versions of the environment.
And here your obedient servant saw the release of Netbeans 7.1. I wanted to try to see the novelty.
First has updated (Slackware Linux 12.2). Launched, opened the project, collected (compiled).
Everything went fine. Advised colleague (Windows 7), he continued to work in the new version.
Then began the unimaginable. The project build went fine, but when executed there was a strange Exception-s. When you click on the Exception the Netbeans editor, opened a blank spot in the code where was a General comment, and not any method.
The Assembly of the same project manually with Ant, and then run from the command line gave a correct result.
it was concluded that Netbeans 7.1 starts some kind of own cache rather than just compiled Java classes!
The conclusion has been proved, do Netbeans has its own cache in the user's home directory. But by cleaning it (deleting the folder .netbeans), and repeated rebuilding of the project, the re-pumping from the version store didn't yield any result. Start in the environment are still made incorrectly. The problem was solved only when the Netbeans project has been re-created and imported all the source code.
However, when it came to upgrading the environment for my colleagues on Windows, something like dancing with the new version started again, lasted a day and to no avail. For Windows project as the same was run correctly, and giving other errors in other places of the code.
In General, we decided to switch to Eclipse. Partly that other developers are using Netbeans 7.0.1.
The first days of development under Eclipse Indigo has left good and bad impressions. Had to configure, create projects based on source code, to get used to another interface.
But it passed, and probably will be transplanted to other Eclipse, because with the environment, giving unpredictable errors due to its own glitches — the enemy does not want.
But still sorry. What is in my opinion inferior to Eclipse, Netbeans is the intuitiveness of the interface.
And generally it is strange how this could happen with proven development environment Netbeans!
Article based on information from habrahabr.ru
The project is already a year and a half.
Until recently, all together used Netbeans IDE. Periodically rejoiced new versions of the environment.
And here your obedient servant saw the release of Netbeans 7.1. I wanted to try to see the novelty.
First has updated (Slackware Linux 12.2). Launched, opened the project, collected (compiled).
Everything went fine. Advised colleague (Windows 7), he continued to work in the new version.
Then began the unimaginable. The project build went fine, but when executed there was a strange Exception-s. When you click on the Exception the Netbeans editor, opened a blank spot in the code where was a General comment, and not any method.
The Assembly of the same project manually with Ant, and then run from the command line gave a correct result.
it was concluded that Netbeans 7.1 starts some kind of own cache rather than just compiled Java classes!
The conclusion has been proved, do Netbeans has its own cache in the user's home directory. But by cleaning it (deleting the folder .netbeans), and repeated rebuilding of the project, the re-pumping from the version store didn't yield any result. Start in the environment are still made incorrectly. The problem was solved only when the Netbeans project has been re-created and imported all the source code.
However, when it came to upgrading the environment for my colleagues on Windows, something like dancing with the new version started again, lasted a day and to no avail. For Windows project as the same was run correctly, and giving other errors in other places of the code.
In General, we decided to switch to Eclipse. Partly that other developers are using Netbeans 7.0.1.
The first days of development under Eclipse Indigo has left good and bad impressions. Had to configure, create projects based on source code, to get used to another interface.
But it passed, and probably will be transplanted to other Eclipse, because with the environment, giving unpredictable errors due to its own glitches — the enemy does not want.
But still sorry. What is in my opinion inferior to Eclipse, Netbeans is the intuitiveness of the interface.
And generally it is strange how this could happen with proven development environment Netbeans!
Комментарии
Отправить комментарий