Simplify disabling / enabling of (custom) package managers

[sschuberth]

It would still be breaking, because disabledPackageManagers trumps enabledPackageManagers, so if you want to use Gradle instead of GradleInspector you would always have to overwrite disabledPackageManagers if we set Gradle as default value.

For future improvement I'm thinking if we should just get rid of those two properties altogether and instead add an enabled property to PackageManagerConfiguration which defaults to true if not set, then we could add a default value in the analyzer config like this:

packageManagers:
  Gradle:
    enabled: false

And if you want to use GradleInspector instead, you would have to configure:

packageManagers:
  Gradle:
    enabled: true
  GradleInspector:
    enabled: false

If required, this could also be supported on the command line if we add an implementation of -P like we already have for the reporter.

Originally posted by @mnonnenmacher in #9944 (comment)

[mnonnenmacher]

I agree, I find it much cleaner to have the enabled flags as part of the package manager configuration instead of the separate properties.

[sschuberth]

I agree, I find it much cleaner to have the enabled flags as part of the package manager configuration instead of the separate properties.

Well, that was your proposal... 😉

So, will you do that follow-up as promised here?

[fviernau]

which defaults to true if not set

Does this mean enabledByDefault will be removed? (Or should enabledByDefault be the default value?)

And if you want to use GradleInspector instead, you would have to configure:

The example following this line is inverted by accident?

Anyway, I like the general direction of the idea.

[sschuberth]

Does this mean enabledByDefault will be removed? (Or should enabledByDefault be the default value?)

It was already removed by 6b507da / 81824ea.

[mnonnenmacher]

So, will you do that follow-up as promised here?

I would be willing to do it, but most likely do not have the time within the next two weeks.