Rename `SbtPgp.settings` to `SbtPgp.pgpSettings` about sbt-pgp HOT 5 CLOSED

Yeah, I still haven't figured out a decent way to do that and keep the plugin as a "user level" install....

Can you let me know what the conflict is now?

from sbt-pgp.

The problem in parboiled is that I have 5 sub-projects underneath the root, of which only 3 need to be published (the others are examples). I'd like to be able to simply say publish-signed on the root level and have the 3 main sub-projects run the task.
Up until sbt-pgp release 0.7 I actively disabled publishing for the 2 example projects by setting publish := () for them. However, with 0.8 setting publish-signed := () doesn't have any effect, because the plugin default settings appear to be set last thereby taking precedence over my futile overriding attempt.

I can see two possible solutions: Either sbt-pgp let's me build up the sub-project settings constructively (i.e. I must be able to explicitly activate them, what this ticket is trying to get across) or SBT must allow me to override the default settings coming in with a plugin. Maybe the latter would be a good thing in any case. You think I should open an SBT ticket for this?

from sbt-pgp.

Ah, yeah, these were my big concerns with moving to publish-signed.

AN sbt feature enhancement is a good idea. Also, I might add a convenient "turn off" setting, like publish := (), but

SettingKeyBoolean := true

Or some such....

from sbt-pgp.

An extra "turn off" setting would fix my particular issue but would also be the least general solution (as the core problem would remain the same for other projectSettings).
I'll add an SBT ticket for enabling overridden plugin default settings...

from sbt-pgp.

So we'll be migrating to AutoPlugins with sbt 0.13.5 which should finally be a way to ensure the PGP settings are turned off. It will always be an "opt-out" plugin as it's meant to be unobtrusive.

from sbt-pgp.