[JENKINS-75032] Add LICENSE file to GitHub repo of LDAP plugin

[jenkins-infra-bot]

We are using that Jenkins plugin in some of the customers so the IT team requests to add a license file.

---

Originally reported by vanashri_intelizign, imported from: Add LICENSE file to GitHub repo of LDAP plugin

• status: Open
• priority: Trivial
• component(s): ldap-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 2025-12-09

Raw content of original issue

We are using that Jenkins plugin in some of the customers so the IT team requests to add a license file.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  The license for the plugin is specified in its pom.xml.  The Apache Maven build process stores the license in the plugin binary.  The license information for all installed plugins can be displayed in Jenkins from the "Manage Jenkins" ==> "About Jenkins" page in the "License and dependency information for plugins" tab.  License information for the plugin is already available for Jenkins users without adding a LICENSE file to the root directory of the source code repository.
  
  If it is important to your organization that there also be a copy of the license in the root directory of the source code repository, you are welcome to submit a pull request that proposes the license text.  Plugin maintainers can then decide if they want to merge your proposed pull request.  If the plugin uses an MIT license, then you can refer to the Jenkins plugin archetype for the LICENSE.md file that is included in plugins created from the archetype.
  
  I've downgraded this issue from Critical to Trivial because the requested improvement does not change the licensing of the plugin and does not help other users of the plugin.
  

The license for the plugin is specified in its pom.xml. The Apache Maven build process stores the license in the plugin binary. The license information for all installed plugins can be displayed in Jenkins from the "Manage Jenkins" ==> "About Jenkins" page in the "License and dependency information for plugins" tab. License information for the plugin is already available for Jenkins users without adding a LICENSE file to the root directory of the source code repository.

If it is important to your organization that there also be a copy of the license in the root directory of the source code repository, you are welcome to submit a pull request that proposes the license text. Plugin maintainers can then decide if they want to merge your proposed pull request. If the plugin uses an MIT license, then you can refer to the Jenkins plugin archetype for the LICENSE.md file that is included in plugins created from the archetype.

I've downgraded this issue from Critical to Trivial because the requested improvement does not change the licensing of the plugin and does not help other users of the plugin.