If the dependency has an MIT license, that is sufficient. No need to include the source code from the dependency.
On Mon, Sep 16, 2019 at 10:48 AM Michael McGreevey < [email protected]> wrote: > My question is about the 2nd bullet item below (found on page: > https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins): > > Specify an open source license <http://opensource.org/licenses/> for your > code (most plugins use MIT) > > - The Jenkins project does not host closed-source plugins > - All of the dependencies of your plugin must also be open > source-licensed > - You should specify the license in the plugin metadata (e.g. pom.xml), > but ideally also in a LICENSE file in the root of your repository > > My plugin has a dependency that has an open source MIT license, is that > sufficient or do I also have to open source the code in this dependency? > > Thank you! > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/b33ddaac-3f50-4396-8a50-451337cd025a%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/b33ddaac-3f50-4396-8a50-451337cd025a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG6HnQnuT_G9qkLe1rXQi9fS6h7sGR9Lk%3DM_qpxk-QUcA%40mail.gmail.com.
