Eclipse Community Forums: Oomph » Disabling oomph rules inherited from the project

Home » Eclipse Projects » Oomph » Disabling oomph rules inherited from the project

Disabling oomph rules inherited from the project [message #1726968]

Thu, 17 March 2016 15:19

Eclipse User

I've been using an oomph workspace created for the JDT install. Each time on startup, it changes a bunch of project settings (the PREF_STRICTLY_COMPATIBLE_JRE preference) which create outgoing changes in my git repsoitory.

Is there any way to use my user or workspace setup files to suppress these rules that are coming in from the project setup (without disabling oomph entirely on startup)?

Re: Disabling oomph rules inherited from the project [message #1726982 is a reply to message #1726968]

Thu, 17 March 2016 20:34

Eclipse User

Stefan,

There were bunch of projects with this option set to error that will
have errors unless the contributor has a whole whack of different JREs
installed. Perhaps that's changed now and we can just remove them.
Note that you should be looking to maintain the Platform.setup somewhere
in the Platform project so you can add or remove what you need without
asking. In the meantime, you can contribute patches to remove the
project-specific preference tasks for the ones that are no longer needed.

On 18.03.2016 03:19, Stefan Xenos wrote:
> I've been using an oomph workspace created for the JDT install. Each
> time on startup, it changes a bunch of project settings (the
> PREF_STRICTLY_COMPATIBLE_JRE preference) which create outgoing changes
> in my git repsoitory.
>
> Is there any way to use my user or workspace setup files to suppress
> these rules that are coming in from the project setup (without disabling
> oomph entirely on startup)?

Re: Disabling oomph rules inherited from the project [message #1727806 is a reply to message #1726982]

Sun, 27 March 2016 15:53

Eclipse User

> There were bunch of projects with this option set to error that will have errors unless the contributor has a whole whack of different JREs installed.

Oh yes. I'm aware of that, but I'm one of the users who went to the trouble of installing a whole whack of different JREs in order to make the errors go away. So are most of the JDT committers - and for those of us that did, we need a way to opt out of the oomph rule that keeps flipping the preference. It seems reasonable for Oomph to flip the preference by default so that not everyone needs to install the JREs. I'm looking for a way for the end-user to opt out, not making a request to change the default. Does such a thing exist?

[Updated on: Sun, 27 March 2016 16:36] by Moderator

Re: Disabling oomph rules inherited from the project [message #1727807 is a reply to message #1727806]

Sun, 27 March 2016 15:57

Eclipse User

> Note that you should be looking to maintain the Platform.setup somewhere
> in the Platform project so you can add or remove what you need without asking.

I think I've already extracted all the platform setup files that I have commit rights for. The root one should probably be owned by the platform releng project, which I'm not a committer on.

Previous Topic:	Eclipse Installer does not work due to a previous installation
Next Topic:	Edit: Can Oomph import a project from TFVC?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 16:47:12 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter