|
|
|
|
| Re: Eclipse for Java development? [message #1862477 is a reply to message #1859055] |
Wed, 06 December 2023 22:43  |
 Gregory Carter
Messages: 3
Registered: July 2023 |
Junior Member |
|
|
In general just some advice:
Eclipse is not a stable IDE and not one for beginners. It is free though! So if you don't like the poor documentation or the frustration of having to use it or eating your projects for lunch occasionally, please consider IntelliJ. I use both and like them both. But I cut my teeth on IntelliJ first then tried Eclipse out, in this case for Java development/App development PrimeFaces. Java EE development is hard enough, fighting with the IDE is even worse. If you are spending more time fighting Eclipse than writing or learning new code (Java for example) consider starting out with IntelliJ.
Some practical advice and pitfalls:
Keep Eclipse Installs of the same version of eclipse handy, in case you need an older version to distribute to other contributors or other people who want to work on a project. Make it a rule that everyone uses the same version and configurations. Do not attempt to patch or change versions in the middle of projects. Unless you have a real bug that is a blocker.
1) Create a Separate install directory for every Eclipse project! I usually have a separate install directory for Eclipse for each project I am working on. I do that so if something blows up the explosion is limited to just that project and not my other Eclipse projects.
For example in my Eclipse Installation Spaces I have:
2023-EclipseSQLConfig
2023-EclipseSQLConfig-Workspace
2021-EclipseWebSiteLogin
2021-EclipseWebSiteLogin-Workspace
...etc...
2) Don't update Eclipse on any given project while you are in a delivery cycle. This keeps issues away. Sometimes there truly are bugs and you have to update. IN that case EVEN THEN I make another install of the Eclipse and freeze the bugged Eclipse, export my project and then load it on the newer patched Eclipse to see if it resolves the bug.
For example:
2023-EclipseSQLConfig-patchtest
2023-EclipseSQLConfig-Workspace-patchtest
3) Work in VM's. If you can and have the memory and horsepower, not too much to ask these days on the quality of laptops we have now. If you don't want to do the 1 and 2 approach, always make a copy of your VM before you begin work for the day, then use that copy for testing patches etc.
I actually use both methods.
Eclipse Don'ts:
1) Pile all sorts of projects into one Eclipse installation. If something should happen to the workspace or config it will prevent access to a lot of work.
2) If you want to keep speed at the maximum you don't want to have all sorts of projects under one Eclipse installation. (See number 1) Just keep one project under one installation directory.
3) Same goes for memory consumption and Eclipse needs a lot. So you might want to redefine the defaults for Eclipse. I use the following for a wide variety of projects and it works just great.
These settings are in a text file called eclipse.ini
...
-Xms512m
-Xmx16384m
...
This is for a laptop with 32GB of memory minimum. you can reduce the 16384 down to 8192 for a 16GB memory laptop. You might even get by with 4096 for a 16GB laptop as long as you don't run EE servers like Wildfly EE.
If you have less than 16GB of memory I would not run Eclipse for Java Development on Windows as it can cause problems. Linux will work, as I tried with 4GB once with a nice big swap file. Can't say about MacOS.
Good Luck and Have Fun. Merry Christmas. :-)
|
|
|
Powered by
FUDForum. Page generated in 0.02651 seconds
] 
Search
Help
Register
Login
Home
