![]() So it sounds like the only thing you've missed the recording of the profile itself. ![]() Maintaining it in your own Product definition is definitely a way to achieve your goal. The recorder only detects things you change so if you didn't change the profile itself during the process, but only changes to active profile that was chosen, then only the latter is recorded. I'd like to think that Oomph does this very well. Mike Muske wrote on Fri, 02 December 2016 15:13 Hi all, I'm really hoping Oomph is able to facilitate team code formatting standards because it looks like a lot of thought and effort has gone into this tool, and it seems to be the future of Eclipse preference management. Most of the blogs/docs are more interested in explaining how to roll up all your plugins in a distro, which is neat, but not our main requirement. I'm afraid I may be fundamentally misunderstanding Oomph's capabilities. If the installer is pointed at a URL for the tup file, does that mean that Eclipse will check this remote tup file each time it starts to see if it has changed and then update Eclipse accordingly? My hope is that after defining a tup file with formatter and other preferences, I can host it at an HTTP url, and our developers can point the Eclipse installer at it to install the company flavor of Eclipse. We don't want to maintain multiple tup files every time a format setting changes. We don't work on code external to our company, we always use the same formatter. I've seen comments on the forum and in blog articles about using project settings for formatter preferences, but we don't want to do that. Is there a way to include the profile in the setup file as well? The problem I ran into with the formatter is that the only preference the Oomph recorder saved was the profile name that is selected. I was then trying to populate it with User Preferences by first recording preference changes into my tup file, and then copying those into the tup file. I tried to achieve this by creating my own tup file with all the plugins/repos we use. This way a team lead can modify the central code format profile and the change will be pushed to every dev's eclipse the next time it starts up (or better yet at some polling interval). Initially I looked at Workspace Mechanic and the Common Preferences plugin, but these seem to have died off after Oomph was introduced - presumably because Oomph does the same things better and offers additional capabilities?īasically what we are trying to achieve is to define a global code format profile, and use a tool (like Oomph) to keep all of the developers' environments up to date with the central definition. I am attempting to setup code formatting preferences for my company that are identical across all of our projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |