Skip to content

Make plugin Group IDs optional in the YAML specification #171

@oleg-nenashev

Description

@oleg-nenashev

Custom WAR Packager 2.x uses the Jenkins update center to retrieve the plugin information, and it can also do pluginID => groupId/artifactId mapping . There is no need to strictly require Group IDs in the current Custom WAR Packager implementation.

Acceptance criteria

  • groupId field is now optional when Update Center Plugin plugin info Provider s used
  • There is a groupId resolution logic in Custom WAR Packager. This logic is invoked if there is no Group ID is specified for a plugin field
  • There is a test coverage for specifications without Group ID

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions