|
|
I have been moving from the classic SAP GUI editor to Eclipse for my ABAP work, and I would like to hear how others set up a professional Eclipse ABAP development tool environment. As far as I understand, the standard choice is ABAP Development Tools (ADT), the SAP plugin for Eclipse, which gives you code completion, quick fixes, refactoring, a built-in debugger, ABAP Unit tests, ATC checks and support for CDS views and RAP objects, all in one workspace. After installing Eclipse and the ADT plugin from SAP's update site, I added a project connection to the system, set up the code templates and kept the keyboard shortcuts close to the ones I already knew. For beginners, I found a plain explanation of the [professional Eclipse ABAP development tool helpful for understanding what ADT can do before touching a real system.
A few questions for the group. Which Eclipse version and Java setup do you use, and have you hit compatibility problems after SAP updates? Do you keep separate workspaces for each system or one for everything? Which extra plugins do you find useful, such as Git integration with abapGit, code formatters or theme and font tweaks? And how do you handle ATC and unit test runs before a transport, so problems are caught early? I would also love tips from people who made the switch from SE80 or SE38, especially about what felt slower at first and what finally made Eclipse the faster option. Thank you for sharing your experience. |
|