[ https://issues.apache.org/jira/browse/HBASE-21371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661560#comment-16661560 ]
Wei-Chiu Chuang commented on HBASE-21371: ----------------------------------------- yes, this will need to be done wherever we ship the relevant jar. if we already have bouncycastle as a dependency shouldn't we have an entry for it though? I've checked the so called "Bouncy Castle License" is literally the same as the MIT License, character-by-character. Interestingly I found LICENSE.vm contains this hard coded license text: {quote}Bouncycastle is released under the MIT license (available above), and is Copyright (c) 2000 - 2006 The Legion Of The Bouncy Castle. {quote} Maybe there's a bug in the license checker plugin and it didn't find Bouncycastle before so you had to manually add this license text? > Hbase unable to compile against Hadoop trunk (3.3.0-SNAPSHOT) due to license > error > ---------------------------------------------------------------------------------- > > Key: HBASE-21371 > URL: https://issues.apache.org/jira/browse/HBASE-21371 > Project: HBase > Issue Type: Bug > Reporter: Wei-Chiu Chuang > Assignee: Wei-Chiu Chuang > Priority: Major > Attachments: HBASE-21371.master.001.patch > > > Hadoop 3.3.0 (trunk) updated various dependencies, which adds additional > licenses that break HBase's license check plugin. > CDDL/GPLv2+CE license > {quote}This product includes JavaBeans Activation Framework API jar licensed > under the CDDL/GPLv2+CE. > CDDL or GPL version 2 plus the Classpath Exception > ERROR: Please check ^^^^^^^^^^^^ this License for acceptability here: > [https://www.apache.org/legal/resolved] > If it is okay, then update the list named 'non_aggregate_fine' in the > LICENSE.vm file. > If it isn't okay, then revert the change that added the dependency. > More info on the dependency: > <groupId>javax.activation</groupId> > <artifactId>javax.activation-api</artifactId> > <version>1.2.0</version> > maven central search > g:javax.activation AND a:javax.activation-api AND v:1.2.0 > project website > [http://java.net/all/javax.activation-api/] > project source > [https://github.com/javaee/activation/javax.activation-api] > {quote} > Bouncy Castle License > {quote}– > This product includes Bouncy Castle PKIX, CMS, EAC, TSP, PKCS, OCSP, CMP, > and CRMF APIs licensed under the Bouncy Castle Licence. > ERROR: Please check ^^^^^^^^^^^^ this License for acceptability here: > [https://www.apache.org/legal/resolved] > If it is okay, then update the list named 'non_aggregate_fine' in the > LICENSE.vm file. > If it isn't okay, then revert the change that added the dependency. > More info on the dependency: > <groupId>org.bouncycastle</groupId> > <artifactId>bcpkix-jdk15on</artifactId> > <version>1.60</version> > maven central search > g:org.bouncycastle AND a:bcpkix-jdk15on AND v:1.60 > project website > [http://www.bouncycastle.org/java.html] > project source > [https://github.com/bcgit/bc-java] > – > {quote} > > And a long list of "Apache Software License - Version 2.0" licensed Jetty > dependencies like this: > {quote} > This product includes Jetty :: Servlet Annotations licensed under the Apache > Software License - Version 2.0. > ERROR: Please check ^^^^^^^^^^^^ this License for acceptability here: > [https://www.apache.org/legal/resolved] > If it is okay, then update the list named 'non_aggregate_fine' in the > LICENSE.vm file. > If it isn't okay, then revert the change that added the dependency. > More info on the dependency: > <groupId>org.eclipse.jetty</groupId> > <artifactId>jetty-annotations</artifactId> > <version>9.3.19.v20170502</version> > maven central search > g:org.eclipse.jetty AND a:jetty-annotations AND v:9.3.19.v20170502 > project website > [http://www.eclipse.org/jetty] > project source > [https://github.com/eclipse/jetty.project/jetty-annotations] > {quote} -- This message was sent by Atlassian JIRA (v7.6.3#76005)