![]() ![]() Host the formatter and cleanup configs somewhere and add a config step in the developer guide.Choose Java > Code Style > Formatter (see above). ![]() Create a bare bones Oomph profile that includes these settings by default and direct developers there. In Eclipse, choose Window menu > Preferences: In the Filter text box, type formatter.later PRs with proper settings will result in convoluted commits that are a mixture of code changes and raw formatting changes that were never applied in old commits.formatting issues will creep in and cause PR churn.My concern is that this will create a lot of extra work for PR reviews as But Save Actions is a manual process which is quite tedious (comparing screenshots of my old Oomph env to my new workspace). Right-click the project, choose 'Properties', then 'Java -> Formatter', check 'enable project specific settings', and configure your formatter however you want. Code Formatter and Code Cleanup settings can be imported from the filesystem (I swear there used to be a URL optional as well, but I don’t see it anymore). Another option for you might be configuring Adapter for Eclipse. With the new approach, we are starting with a vanilla eclipse install, so all of this configuration must be done manually. The indent size for parameter descriptions is defined by the 'Continuation indent' value (Settings/Preferences -> Editor -> Code Style -> Java -> Tabs and Indents) That will affect more than just parameter descriptions, though, so Im not sure if that would work for you. One advantage of the old setup approach via Oomph was that it automatically configured the ESH profiles for Code Formatter, Code Cleanup, and Save Actions. I’ve started migrating my development environment over to maven/bnd per
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |