Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69049

ability for a pure API plugin to skip detached dependencies

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Duplicate
    • core
    • None

    Description

      As a developer of a pure API plugin (one that depends on some libraries but not on anything in Jenkins core) I want to be able to have a clean plugin with no implied detached dependencies regardless of the jenkins core I am targetting.

      As we are detaching things from core we will install those versions of plugins if a plugin is installed that depends on an old version of core when it is upgraded.

      However if the plugin is a pure api plugin there is never any need to consider detached plugins and sometimes this causes an issue (JENKINS-69034)

      Whilst a developer can constantly update thier Jenkins baseline - I would not want to update it (and release) to a version that is not an LTS so the above issue could still be a problem for users.

      As a plugin developer I should be able to add a pom.xml configuration that states this plugin will never need any detached plugins as it uses nothing from core.

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick added a comment -

            Basically the same as JENKINS-28942, though stated as being restricted to pure library wrapper plugins.

            jglick Jesse Glick added a comment - Basically the same as JENKINS-28942 , though stated as being restricted to pure library wrapper plugins.

            People

              Unassigned Unassigned
              teilo James Nord
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: