You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it's hard to use a plugin only for publishing. Especially when the publishing process happens only on CI. At this point, a valid token is not needed locally.
But the build will fail anyway since the credentials setting requires a token to be defined.
From my point of view, the functionality can be separated into smaller modules.
Currently, it's hard to use a plugin only for publishing. Especially when the publishing process happens only on CI. At this point, a valid token is not needed locally.
But the build will fail anyway since the
credentials
setting requires a token to be defined.From my point of view, the functionality can be separated into smaller modules.
Project modules:
Publisher
Resolver
Publisher
andResolver
. Identical to the current definition.Publisher
Responsible for the publishing part.
Settings:
githubSuppressPublicationWarning
githubPublishToRepository
- The entry is a combination of owner, repository, and token source.Derived settings (based on
githubPublishToRepository
):githubPublishTo
scmInfo
homepage
pomIncludeRepository
publishMavenStyle
Behavior:
update
- does not fail if a token is missingpublish
- may fail if a token is missingResolver/Downloader/Loader
The should be a better name I believe.
It would be nice if multiple GitHub repositories can be supported.
Settings:
githubRepositories
- The GitHub repositories. The entry is a combination of owner, repository, and token source.Derived settings (based on
githubRepositories
):resolvers
credentials
Behavior:
update
- may fail if a token is missingThe text was updated successfully, but these errors were encountered: