Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: nunit-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.64 on CentOS 7
    • Similar Issues:

      Description

      An explicit license in the pom.xml or LICENSE.txt in the NUnit Plugin repo would be very helpful. My CI team would like to use this plugin and our legal department is uneasy about it (I'm aware of the licensing terms under https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin).

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          Fixed in 0.21

          Show
          slide_o_mix Alex Earl added a comment - Fixed in 0.21
          Hide
          jbowen Jason Bowen added a comment -

          According to the link in the description, since there is not a license header at the top of the source files, no LICENSE file at the root of the repo, and no license in the <Licenses> section of the pom.xml, the project falls under the MIT license.

          Unless there are parts of your code that are explicitly licensed under other terms, if you are the maintainer then I would expect you can select a license (of course I'm not a legal scholar, so take that with a grain of salt).

          Is it possible for you to contact the Jenkins project to seek advice for this situation? I'm hoping I can convince my legal department that the code is licensed under the MIT license per the noted wiki page, but an explicit license in the repo for the plugin would make things much more clear for everyone.

          Show
          jbowen Jason Bowen added a comment - According to the link in the description, since there is not a license header at the top of the source files, no LICENSE file at the root of the repo, and no license in the <Licenses> section of the pom.xml, the project falls under the MIT license. Unless there are parts of your code that are explicitly licensed under other terms, if you are the maintainer then I would expect you can select a license (of course I'm not a legal scholar, so take that with a grain of salt). Is it possible for you to contact the Jenkins project to seek advice for this situation? I'm hoping I can convince my legal department that the code is licensed under the MIT license per the noted wiki page, but an explicit license in the repo for the plugin would make things much more clear for everyone.
          Hide
          slide_o_mix Alex Earl added a comment -

          I took over this plugin from someone else. IANAL, so I don't know if I can just choose a license or not.

          Show
          slide_o_mix Alex Earl added a comment - I took over this plugin from someone else. IANAL, so I don't know if I can just choose a license or not.

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              jbowen Jason Bowen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: