You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by Ruilong Huo <rh...@pivotal.io> on 2017/05/15 07:12:02 UTC
Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Hi Roman,
Currently I am preparing LICENSE, NOTICE, and DISCLAIMER files for Apache
HAWQ 2.2.0.0-incubating rpm binary release. The components of the binary
package
<https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
are as below:
*> tar -xzvf apache-hawq-rpm-2.2.0.0-incubating.tar.gz; tree
hawq_rpm_packages*
hawq_rpm_packages
├── apache-hawq-2.2.0.0-el7.x86_64.rpm
├── apache-tomcat-7.0.62-el6.noarch.rpm
├── hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm
├── pxf-3.2.1.0-1.el6.noarch.rpm
├── pxf-hbase-3.2.1.0-1.el6.noarch.rpm
├── pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
├── pxf-hive-3.2.1.0-1.el6.noarch.rpm
├── pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
├── pxf-json-3.2.1.0-1.el6.noarch.rpm
└── pxf-service-3.2.1.0-1.el6.noarch.rpm
Given the LICENSE, NOTICE, and DISCLAIMER for Apache HAWQ source in top
directory:
*> tree incubator-hawq/*
incubator-hawq/
├── DISCLAIMER
├── LICENSE
└── NOTICE
We plan to put LICENSE, NOTICE, and DISCLAIMER for binary release in a
dedicated directory named dist which under top directory. Then these files
will be copied to the rpm packages in packaging stage.
Here are two options for the layout of the LICENSE, NOTICE, and DISCLAIMER
for the components:
*Option 1: Combine the licenses of all the components into one LICENSE,
NOTICE, and DISCLAIMER respectively. For example:*
*> cd $APACHE_HAWQ_TOP_DIR; tree dist*
dist
├── DISCLAIMER
├── LICENSE
└── NOTICE
*Option 2: Keep the separated LICENSE, NOTICE, and DISCLAIMER for each of
the components. For example:*
*> cd $APACHE_HAWQ_TOP_DIR; tree dist/*
dist/
├── hawq
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf-hbase
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf-hdfs
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf-hive
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf-jdbc
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf-json
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── pxf-service
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
├── ranger-plugin
│ ├── DISCLAIMER
│ ├── LICENSE
│ └── NOTICE
└── tomcat
├── DISCLAIMER
├── LICENSE
└── NOTICE
For option 1, it is easier to maintain the LICENSE, NOTICE, and DISCLAIMER
files. However, it contains all the licenses for all the components. Thus
it is hard to identify which component contains what licenses.
For option 2, it needs extra maintenance effort. But, it is clear that what
are the licenses for each of the components.
Would you please share you comments and let us know which is better? Thanks.
Best regards,
Ruilong Huo
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Lei Chang <ch...@gmail.com>.
I think Option 2 is better, more clear.
Cheers
Lei
On Mon, May 22, 2017 at 10:15 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> Please let us know if you get a chance to review this. Or someone else who
> can help on this? Thanks.
>
> Best regards,
> Ruilong Huo
>
> On Mon, May 15, 2017 at 3:12 PM, Ruilong Huo <rh...@pivotal.io> wrote:
>
> > Hi Roman,
> >
> > Currently I am preparing LICENSE, NOTICE, and DISCLAIMER files for Apache
> > HAWQ 2.2.0.0-incubating rpm binary release. The components of the binary
> > package
> > <https://dist.apache.org/repos/dist/dev/incubator/hawq/
> 2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> > are as below:
> >
> > *> tar -xzvf apache-hawq-rpm-2.2.0.0-incubating.tar.gz; tree
> > hawq_rpm_packages*
> > hawq_rpm_packages
> > ├── apache-hawq-2.2.0.0-el7.x86_64.rpm
> > ├── apache-tomcat-7.0.62-el6.noarch.rpm
> > ├── hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm
> > ├── pxf-3.2.1.0-1.el6.noarch.rpm
> > ├── pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> > ├── pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> > ├── pxf-hive-3.2.1.0-1.el6.noarch.rpm
> > ├── pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> > ├── pxf-json-3.2.1.0-1.el6.noarch.rpm
> > └── pxf-service-3.2.1.0-1.el6.noarch.rpm
> >
> > Given the LICENSE, NOTICE, and DISCLAIMER for Apache HAWQ source in top
> > directory:
> >
> > *> tree incubator-hawq/*
> > incubator-hawq/
> > ├── DISCLAIMER
> > ├── LICENSE
> > └── NOTICE
> >
> > We plan to put LICENSE, NOTICE, and DISCLAIMER for binary release in a
> > dedicated directory named dist which under top directory. Then these
> files
> > will be copied to the rpm packages in packaging stage.
> >
> > Here are two options for the layout of the LICENSE, NOTICE, and
> DISCLAIMER
> > for the components:
> >
> > *Option 1: Combine the licenses of all the components into one LICENSE,
> > NOTICE, and DISCLAIMER respectively. For example:*
> >
> > *> cd $APACHE_HAWQ_TOP_DIR; tree dist*
> > dist
> > ├── DISCLAIMER
> > ├── LICENSE
> > └── NOTICE
> >
> > *Option 2: Keep the separated LICENSE, NOTICE, and DISCLAIMER for each of
> > the components. For example:*
> >
> > *> cd $APACHE_HAWQ_TOP_DIR; tree dist/*
> > dist/
> > ├── hawq
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf-hbase
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf-hdfs
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf-hive
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf-jdbc
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf-json
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── pxf-service
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > ├── ranger-plugin
> > │ ├── DISCLAIMER
> > │ ├── LICENSE
> > │ └── NOTICE
> > └── tomcat
> > ├── DISCLAIMER
> > ├── LICENSE
> > └── NOTICE
> >
> > For option 1, it is easier to maintain the LICENSE, NOTICE, and
> DISCLAIMER
> > files. However, it contains all the licenses for all the components. Thus
> > it is hard to identify which component contains what licenses.
> >
> > For option 2, it needs extra maintenance effort. But, it is clear that
> > what are the licenses for each of the components.
> >
> > Would you please share you comments and let us know which is better?
> > Thanks.
> >
> > Best regards,
> > Ruilong Huo
> >
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ed Espino <es...@apache.org>.
Everyone, thanks for your input on this. We will get started on enhancing
the PXF build processes to adhere to the Apache binary release
requirements. I believe we now have a line of sight to releasing our
initial Apache HAWQ incubating convenience binary release.
Regards,
-=e
On Tue, Jun 6, 2017 at 9:52 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Tue, Jun 6, 2017 at 12:21 AM, Ed Espino <es...@apache.org> wrote:
> > Roman,
> >
> > If we cannot resolve the Ranger licensing issues in a reasonable
> timeframe,
> > do you feel it would be helpful to provide the HAWQ optional Ranger
> support
> > in a subsequent convenience binary release? The project is learning a
> > considerable amount on the binary release process. To keep the project
> > momentum, I feel it will help to complete the HAWQ C/C++ and PXF
> components
> > at this point.
> >
> > Thoughts?
>
> I think that's a very good idea, indeed! +1
>
> Thanks,
> Roman.
>
--
*Ed Espino*
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, Jun 6, 2017 at 12:21 AM, Ed Espino <es...@apache.org> wrote:
> Roman,
>
> If we cannot resolve the Ranger licensing issues in a reasonable timeframe,
> do you feel it would be helpful to provide the HAWQ optional Ranger support
> in a subsequent convenience binary release? The project is learning a
> considerable amount on the binary release process. To keep the project
> momentum, I feel it will help to complete the HAWQ C/C++ and PXF components
> at this point.
>
> Thoughts?
I think that's a very good idea, indeed! +1
Thanks,
Roman.
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Vineet Goel <vv...@apache.org>.
Ed, +1 to that idea. Ranger component is technically optional and I think
we should release without it and resolve that in the next version. This
will keep the momentum going ...
Thanks
On Tue, Jun 6, 2017 at 12:22 AM Ed Espino <es...@apache.org> wrote:
> Roman,
>
> If we cannot resolve the Ranger licensing issues in a reasonable timeframe,
> do you feel it would be helpful to provide the HAWQ optional Ranger support
> in a subsequent convenience binary release? The project is learning a
> considerable amount on the binary release process. To keep the project
> momentum, I feel it will help to complete the HAWQ C/C++ and PXF components
> at this point.
>
> Thoughts?
>
> -=ed espino
>
> On Mon, Jun 5, 2017 at 7:38 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > On Mon, Jun 5, 2017 at 7:48 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> > > Hi Roman,
> > >
> > > Please let us know if you have a chance to review the java components
> for
> > > pxf and ranger and share with your feedback. Thanks.
> >
> > Yes I have. Here's what I found out:
> > 1. For PXF all you have to do at this point is to make sure that each
> > JAR/WAR
> > files that gets shipped has LICENSE, NOTICE and DISCLAIMER
> embedded
> > in its META-INF/ folder in the JAR itself. Given that PXF doesn't
> > seem
> > to bundle any extra bits -- that should get you clear for JARs
> >
> > 2. For Ranger plugin it gets more complicated. I will start by
> > making sure that all
> > the JAR/WAR files that are produced by HAWQ itself get the same
> > treatment
> > as PXF does in #1. That still won't get you off the hook though
> > for RPMs, because
> > it seems that RPMs re-ship a LOT of dependencies. For those
> > dependencies I'd
> > recommend having a build script that extracts LICENSE, NOTICE
> > and DISCLAIMER
> > (if any) from all the bundled JARs/WARs (things under
> > plugin-service/lib for example)
> > and places them in a special folder within the RPM itself.
> >
> > So as long as you do that and make sure that LICENSE, NOTICE and
> DISCLAIMER
> > find their way into all of the RPMs (regardless of whether they
> > contain C/C++ binaries
> > of JARs/WARs) you should be good for your next release.
> >
> > Makes sense?
> >
> > Thanks,
> > Roman.
> >
>
>
>
> --
> *Ed Espino*
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ed Espino <es...@apache.org>.
Roman,
If we cannot resolve the Ranger licensing issues in a reasonable timeframe,
do you feel it would be helpful to provide the HAWQ optional Ranger support
in a subsequent convenience binary release? The project is learning a
considerable amount on the binary release process. To keep the project
momentum, I feel it will help to complete the HAWQ C/C++ and PXF components
at this point.
Thoughts?
-=ed espino
On Mon, Jun 5, 2017 at 7:38 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Mon, Jun 5, 2017 at 7:48 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> > Hi Roman,
> >
> > Please let us know if you have a chance to review the java components for
> > pxf and ranger and share with your feedback. Thanks.
>
> Yes I have. Here's what I found out:
> 1. For PXF all you have to do at this point is to make sure that each
> JAR/WAR
> files that gets shipped has LICENSE, NOTICE and DISCLAIMER embedded
> in its META-INF/ folder in the JAR itself. Given that PXF doesn't
> seem
> to bundle any extra bits -- that should get you clear for JARs
>
> 2. For Ranger plugin it gets more complicated. I will start by
> making sure that all
> the JAR/WAR files that are produced by HAWQ itself get the same
> treatment
> as PXF does in #1. That still won't get you off the hook though
> for RPMs, because
> it seems that RPMs re-ship a LOT of dependencies. For those
> dependencies I'd
> recommend having a build script that extracts LICENSE, NOTICE
> and DISCLAIMER
> (if any) from all the bundled JARs/WARs (things under
> plugin-service/lib for example)
> and places them in a special folder within the RPM itself.
>
> So as long as you do that and make sure that LICENSE, NOTICE and DISCLAIMER
> find their way into all of the RPMs (regardless of whether they
> contain C/C++ binaries
> of JARs/WARs) you should be good for your next release.
>
> Makes sense?
>
> Thanks,
> Roman.
>
--
*Ed Espino*
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Jun 5, 2017 at 7:48 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> Please let us know if you have a chance to review the java components for
> pxf and ranger and share with your feedback. Thanks.
Yes I have. Here's what I found out:
1. For PXF all you have to do at this point is to make sure that each JAR/WAR
files that gets shipped has LICENSE, NOTICE and DISCLAIMER embedded
in its META-INF/ folder in the JAR itself. Given that PXF doesn't seem
to bundle any extra bits -- that should get you clear for JARs
2. For Ranger plugin it gets more complicated. I will start by
making sure that all
the JAR/WAR files that are produced by HAWQ itself get the same treatment
as PXF does in #1. That still won't get you off the hook though
for RPMs, because
it seems that RPMs re-ship a LOT of dependencies. For those
dependencies I'd
recommend having a build script that extracts LICENSE, NOTICE
and DISCLAIMER
(if any) from all the bundled JARs/WARs (things under
plugin-service/lib for example)
and places them in a special folder within the RPM itself.
So as long as you do that and make sure that LICENSE, NOTICE and DISCLAIMER
find their way into all of the RPMs (regardless of whether they
contain C/C++ binaries
of JARs/WARs) you should be good for your next release.
Makes sense?
Thanks,
Roman.
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
Hi Roman,
Please let us know if you have a chance to review the java components for
pxf and ranger and share with your feedback. Thanks.
Best regards,
Ruilong Huo
On Thu, Jun 1, 2017 at 7:36 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> The LICENSE, NOTICE, and DISCLAIMER files for hawq c/c++ components are
> available for review at PR #1246
> <https://github.com/apache/incubator-hawq/pull/1246>. Please find my
> clarification for your comments there.
>
> Please let us know if you have any feedback for java components (i.e.,
> pxf, ranger) so that we can prepare LICENSE, NOTICE, and DISCLAIMER files
> for them in separate PR.
>
> Best regards,
> Ruilong Huo
>
> On Wed, May 31, 2017 at 10:40 AM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> It seems I need to spend a bit more time with Ranger artifact -- let
>> me tinker some
>> more and I'll let you guys know.
>>
>> In the meantime, I propose we go ahead with declaring C/C++ binary
>> dependencies
>> in our LICENSE/NOTICE.
>>
>> Thanks,
>> Roman.
>>
>> On Fri, May 26, 2017 at 10:06 PM, Ruilong Huo <rh...@pivotal.io> wrote:
>> > Hi Roman,
>> >
>> > The stax-api and jabx-impl are bundled in Ranger, NOT PXF. To be
>> specific,
>> > they are in hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm which
>> is in
>> > apache-hawq-rpm-2.2.0.0-incubating.tar.gz
>> > <https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.
>> 0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
>> > .
>> > You can get them with "rpm2cpio
>> > hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm | cpio -div".
>> >
>> > The details of the dependency shows that: stax-api and jabx-impl is
>> > dependency of hadoop-common, while hadoop-common is dependency ranger
>> > plugin in hawq.
>> >
>> > *$ mvn project-info-reports:dependencies*
>> > *[INFO] Scanning for projects...*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO] Reactor Build Order:*
>> > *[INFO]*
>> > *[INFO] HAWQ Ranger Plugin*
>> > *[INFO] HAWQ Ranger Admin Plugin*
>> > *[INFO] HAWQ Ranger Service*
>> > *[INFO]*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO] Building HAWQ Ranger Admin Plugin 2.2.0.0*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO]*
>> > *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
>> > ranger-plugin-admin ---*
>> > *[INFO] org.apache.hawq:ranger-plugin-admin:jar:2.2.0.0*
>> > *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
>> > *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
>> > *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
>> > *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
>> > *[INFO] | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
>> > *[INFO] | | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
>> > *[INFO] | | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
>> > *[INFO] | | | | \- javax.activation:activation:jar:1.1:compile*
>> > *[INFO] ......*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO] Building HAWQ Ranger Service 2.2.0.0*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO]*
>> > *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
>> > ranger-plugin-service ---*
>> > *[INFO] org.apache.hawq:ranger-plugin-service:war:2.2.0.0*
>> > *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
>> > *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
>> > *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
>> > *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
>> > *[INFO] | | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
>> > *[INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
>> > *[INFO] | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
>> > *[INFO] | | | \- javax.activation:activation:jar:1.1:compile*
>> > *[INFO] ......*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO] Reactor Summary:*
>> > *[INFO]*
>> > *[INFO] HAWQ Ranger Plugin ................................. SUCCESS [
>> > 0.425 s]*
>> > *[INFO] HAWQ Ranger Admin Plugin ........................... SUCCESS [
>> > 0.252 s]*
>> > *[INFO] HAWQ Ranger Service ................................ SUCCESS [
>> > 0.099 s]*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO] BUILD SUCCESS*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> > *[INFO] Total time: 0.992 s*
>> > *[INFO] Finished at: 2017-05-22T17:24:15+08:00*
>> > *[INFO] Final Memory: 19M/437M*
>> > *[INFO]
>> > ------------------------------------------------------------
>> ------------*
>> >
>> > Best regards,
>> > Ruilong Huo
>> >
>> > On Sat, May 27, 2017 at 7:32 AM, Roman Shaposhnik <roman@shaposhnik.org
>> >
>> > wrote:
>> >
>> >> On Fri, May 26, 2017 at 8:11 AM, Ruilong Huo <rh...@pivotal.io> wrote:
>> >> > Hi Roman,
>> >> >
>> >> > Thanks for your feedback!
>> >> >
>> >> > We will merge the license information for the C/C++ components and
>> >> prepare
>> >> > LICENSE and NOTICE files accordingly.
>> >>
>> >> Great! Let me know when can I review the actual files.
>> >>
>> >> > As for JSON in PXF which is incompatible with ASL v2, the fix is to
>> >> replace
>> >> > it with some library which is compatible or remove it?
>> >>
>> >> Correct. Here's a list of alternative libraries you should start
>> migrating
>> >> to:
>> >> https://wiki.debian.org/qa.debian.org/jsonevil
>> >>
>> >> There's also http://johnzon.apache.org/
>> >>
>> >> And finally:
>> >>
>> >> <dependency>
>> >> <groupId>com.tdunning</groupId>
>> >> <artifactId>json</artifactId>
>> >> <version>1.0</version>
>> >> </dependency>
>> >>
>> >> > Furthermore, Hongxu helped to get the license information for Ranger
>> as
>> >> > well and it turns out that there two dependencies with GPL license
>> which
>> >> is
>> >> > also not compatible with ASL v2:
>> >> >
>> >> > 1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API
>> that
>> >> > allows you to stream XML data from and to your application.
>> >> >
>> >> > 2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
>> >> > Contains sources required for runtime processing.
>> >> >
>> >> > They are actually directly required by hadoop common and thus is
>> >> indirectly
>> >> > required by HAWQ Ranger.
>> >>
>> >> I still need to double check it -- but I think those just bring in the
>> >> APIs which
>> >> get replaced during the runtime. Will take a deeper look, though.
>> >>
>> >> > They are bundled hawq binary during packaging with
>> >> > maven.
>> >>
>> >> Wait. Where are they bundled? I don't see them as part of PXF?
>> >
>> >
>> >
>> >
>> >> Thanks,
>> >> Roman.
>> >>
>>
>
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
The LICENSE, NOTICE, and DISCLAIMER files for hawq c/c++ components are
available for review at PR #1246
<https://github.com/apache/incubator-hawq/pull/1246>. Please find my
clarification for your comments there.
Please let us know if you have any feedback for java components (i.e., pxf,
ranger) so that we can prepare LICENSE, NOTICE, and DISCLAIMER files for
them in separate PR.
Best regards,
Ruilong Huo
On Wed, May 31, 2017 at 10:40 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> It seems I need to spend a bit more time with Ranger artifact -- let
> me tinker some
> more and I'll let you guys know.
>
> In the meantime, I propose we go ahead with declaring C/C++ binary
> dependencies
> in our LICENSE/NOTICE.
>
> Thanks,
> Roman.
>
> On Fri, May 26, 2017 at 10:06 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> > Hi Roman,
> >
> > The stax-api and jabx-impl are bundled in Ranger, NOT PXF. To be
> specific,
> > they are in hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm which is
> in
> > apache-hawq-rpm-2.2.0.0-incubating.tar.gz
> > <https://dist.apache.org/repos/dist/dev/incubator/hawq/
> 2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> > .
> > You can get them with "rpm2cpio
> > hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm | cpio -div".
> >
> > The details of the dependency shows that: stax-api and jabx-impl is
> > dependency of hadoop-common, while hadoop-common is dependency ranger
> > plugin in hawq.
> >
> > *$ mvn project-info-reports:dependencies*
> > *[INFO] Scanning for projects...*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO] Reactor Build Order:*
> > *[INFO]*
> > *[INFO] HAWQ Ranger Plugin*
> > *[INFO] HAWQ Ranger Admin Plugin*
> > *[INFO] HAWQ Ranger Service*
> > *[INFO]*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO] Building HAWQ Ranger Admin Plugin 2.2.0.0*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO]*
> > *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> > ranger-plugin-admin ---*
> > *[INFO] org.apache.hawq:ranger-plugin-admin:jar:2.2.0.0*
> > *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
> > *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
> > *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
> > *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
> > *[INFO] | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
> > *[INFO] | | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
> > *[INFO] | | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
> > *[INFO] | | | | \- javax.activation:activation:jar:1.1:compile*
> > *[INFO] ......*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO] Building HAWQ Ranger Service 2.2.0.0*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO]*
> > *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> > ranger-plugin-service ---*
> > *[INFO] org.apache.hawq:ranger-plugin-service:war:2.2.0.0*
> > *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
> > *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
> > *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
> > *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
> > *[INFO] | | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
> > *[INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
> > *[INFO] | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
> > *[INFO] | | | \- javax.activation:activation:jar:1.1:compile*
> > *[INFO] ......*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO] Reactor Summary:*
> > *[INFO]*
> > *[INFO] HAWQ Ranger Plugin ................................. SUCCESS [
> > 0.425 s]*
> > *[INFO] HAWQ Ranger Admin Plugin ........................... SUCCESS [
> > 0.252 s]*
> > *[INFO] HAWQ Ranger Service ................................ SUCCESS [
> > 0.099 s]*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO] BUILD SUCCESS*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> > *[INFO] Total time: 0.992 s*
> > *[INFO] Finished at: 2017-05-22T17:24:15+08:00*
> > *[INFO] Final Memory: 19M/437M*
> > *[INFO]
> > ------------------------------------------------------------
> ------------*
> >
> > Best regards,
> > Ruilong Huo
> >
> > On Sat, May 27, 2017 at 7:32 AM, Roman Shaposhnik <ro...@shaposhnik.org>
> > wrote:
> >
> >> On Fri, May 26, 2017 at 8:11 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> >> > Hi Roman,
> >> >
> >> > Thanks for your feedback!
> >> >
> >> > We will merge the license information for the C/C++ components and
> >> prepare
> >> > LICENSE and NOTICE files accordingly.
> >>
> >> Great! Let me know when can I review the actual files.
> >>
> >> > As for JSON in PXF which is incompatible with ASL v2, the fix is to
> >> replace
> >> > it with some library which is compatible or remove it?
> >>
> >> Correct. Here's a list of alternative libraries you should start
> migrating
> >> to:
> >> https://wiki.debian.org/qa.debian.org/jsonevil
> >>
> >> There's also http://johnzon.apache.org/
> >>
> >> And finally:
> >>
> >> <dependency>
> >> <groupId>com.tdunning</groupId>
> >> <artifactId>json</artifactId>
> >> <version>1.0</version>
> >> </dependency>
> >>
> >> > Furthermore, Hongxu helped to get the license information for Ranger
> as
> >> > well and it turns out that there two dependencies with GPL license
> which
> >> is
> >> > also not compatible with ASL v2:
> >> >
> >> > 1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API
> that
> >> > allows you to stream XML data from and to your application.
> >> >
> >> > 2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
> >> > Contains sources required for runtime processing.
> >> >
> >> > They are actually directly required by hadoop common and thus is
> >> indirectly
> >> > required by HAWQ Ranger.
> >>
> >> I still need to double check it -- but I think those just bring in the
> >> APIs which
> >> get replaced during the runtime. Will take a deeper look, though.
> >>
> >> > They are bundled hawq binary during packaging with
> >> > maven.
> >>
> >> Wait. Where are they bundled? I don't see them as part of PXF?
> >
> >
> >
> >
> >> Thanks,
> >> Roman.
> >>
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
It seems I need to spend a bit more time with Ranger artifact -- let
me tinker some
more and I'll let you guys know.
In the meantime, I propose we go ahead with declaring C/C++ binary dependencies
in our LICENSE/NOTICE.
Thanks,
Roman.
On Fri, May 26, 2017 at 10:06 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> The stax-api and jabx-impl are bundled in Ranger, NOT PXF. To be specific,
> they are in hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm which is in
> apache-hawq-rpm-2.2.0.0-incubating.tar.gz
> <https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> .
> You can get them with "rpm2cpio
> hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm | cpio -div".
>
> The details of the dependency shows that: stax-api and jabx-impl is
> dependency of hadoop-common, while hadoop-common is dependency ranger
> plugin in hawq.
>
> *$ mvn project-info-reports:dependencies*
> *[INFO] Scanning for projects...*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Reactor Build Order:*
> *[INFO]*
> *[INFO] HAWQ Ranger Plugin*
> *[INFO] HAWQ Ranger Admin Plugin*
> *[INFO] HAWQ Ranger Service*
> *[INFO]*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Building HAWQ Ranger Admin Plugin 2.2.0.0*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO]*
> *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> ranger-plugin-admin ---*
> *[INFO] org.apache.hawq:ranger-plugin-admin:jar:2.2.0.0*
> *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
> *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
> *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
> *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
> *[INFO] | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
> *[INFO] | | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
> *[INFO] | | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
> *[INFO] | | | | \- javax.activation:activation:jar:1.1:compile*
> *[INFO] ......*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Building HAWQ Ranger Service 2.2.0.0*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO]*
> *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> ranger-plugin-service ---*
> *[INFO] org.apache.hawq:ranger-plugin-service:war:2.2.0.0*
> *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
> *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
> *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
> *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
> *[INFO] | | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
> *[INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
> *[INFO] | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
> *[INFO] | | | \- javax.activation:activation:jar:1.1:compile*
> *[INFO] ......*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Reactor Summary:*
> *[INFO]*
> *[INFO] HAWQ Ranger Plugin ................................. SUCCESS [
> 0.425 s]*
> *[INFO] HAWQ Ranger Admin Plugin ........................... SUCCESS [
> 0.252 s]*
> *[INFO] HAWQ Ranger Service ................................ SUCCESS [
> 0.099 s]*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] BUILD SUCCESS*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Total time: 0.992 s*
> *[INFO] Finished at: 2017-05-22T17:24:15+08:00*
> *[INFO] Final Memory: 19M/437M*
> *[INFO]
> ------------------------------------------------------------------------*
>
> Best regards,
> Ruilong Huo
>
> On Sat, May 27, 2017 at 7:32 AM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> On Fri, May 26, 2017 at 8:11 AM, Ruilong Huo <rh...@pivotal.io> wrote:
>> > Hi Roman,
>> >
>> > Thanks for your feedback!
>> >
>> > We will merge the license information for the C/C++ components and
>> prepare
>> > LICENSE and NOTICE files accordingly.
>>
>> Great! Let me know when can I review the actual files.
>>
>> > As for JSON in PXF which is incompatible with ASL v2, the fix is to
>> replace
>> > it with some library which is compatible or remove it?
>>
>> Correct. Here's a list of alternative libraries you should start migrating
>> to:
>> https://wiki.debian.org/qa.debian.org/jsonevil
>>
>> There's also http://johnzon.apache.org/
>>
>> And finally:
>>
>> <dependency>
>> <groupId>com.tdunning</groupId>
>> <artifactId>json</artifactId>
>> <version>1.0</version>
>> </dependency>
>>
>> > Furthermore, Hongxu helped to get the license information for Ranger as
>> > well and it turns out that there two dependencies with GPL license which
>> is
>> > also not compatible with ASL v2:
>> >
>> > 1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API that
>> > allows you to stream XML data from and to your application.
>> >
>> > 2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
>> > Contains sources required for runtime processing.
>> >
>> > They are actually directly required by hadoop common and thus is
>> indirectly
>> > required by HAWQ Ranger.
>>
>> I still need to double check it -- but I think those just bring in the
>> APIs which
>> get replaced during the runtime. Will take a deeper look, though.
>>
>> > They are bundled hawq binary during packaging with
>> > maven.
>>
>> Wait. Where are they bundled? I don't see them as part of PXF?
>
>
>
>
>> Thanks,
>> Roman.
>>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
Hi Roman,
Please review the license information for hawq c/c++ components in PR #1246
<https://github.com/apache/incubator-hawq/pull/1246> and let us know your
feedback. Thanks.
The change includes:
1. The LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ c/c++
components for the binary release.
2. The build process to add the LICENSE, NOTICE, and DISCLAIMER files in
Apache HAWQ binary package.
Best regards,
Ruilong Huo
On Sat, May 27, 2017 at 1:06 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> The stax-api and jabx-impl are bundled in Ranger, NOT PXF. To be specific,
> they are in hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm which is
> in apache-hawq-rpm-2.2.0.0-incubating.tar.gz
> <https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> .
> You can get them with "rpm2cpio hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm
> | cpio -div".
>
> The details of the dependency shows that: stax-api and jabx-impl is
> dependency of hadoop-common, while hadoop-common is dependency ranger
> plugin in hawq.
>
> *$ mvn project-info-reports:dependencies*
> *[INFO] Scanning for projects...*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Reactor Build Order:*
> *[INFO]*
> *[INFO] HAWQ Ranger Plugin*
> *[INFO] HAWQ Ranger Admin Plugin*
> *[INFO] HAWQ Ranger Service*
> *[INFO]*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Building HAWQ Ranger Admin Plugin 2.2.0.0*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO]*
> *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> ranger-plugin-admin ---*
> *[INFO] org.apache.hawq:ranger-plugin-admin:jar:2.2.0.0*
> *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
> *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
> *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
> *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
> *[INFO] | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
> *[INFO] | | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
> *[INFO] | | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
> *[INFO] | | | | \- javax.activation:activation:jar:1.1:compile*
> *[INFO] ......*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Building HAWQ Ranger Service 2.2.0.0*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO]*
> *[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> ranger-plugin-service ---*
> *[INFO] org.apache.hawq:ranger-plugin-service:war:2.2.0.0*
> *[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
> *[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
> *[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
> *[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
> *[INFO] | | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
> *[INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
> *[INFO] | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
> *[INFO] | | | \- javax.activation:activation:jar:1.1:compile*
> *[INFO] ......*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Reactor Summary:*
> *[INFO]*
> *[INFO] HAWQ Ranger Plugin ................................. SUCCESS [
> 0.425 s]*
> *[INFO] HAWQ Ranger Admin Plugin ........................... SUCCESS [
> 0.252 s]*
> *[INFO] HAWQ Ranger Service ................................ SUCCESS [
> 0.099 s]*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] BUILD SUCCESS*
> *[INFO]
> ------------------------------------------------------------------------*
> *[INFO] Total time: 0.992 s*
> *[INFO] Finished at: 2017-05-22T17:24:15+08:00*
> *[INFO] Final Memory: 19M/437M*
> *[INFO]
> ------------------------------------------------------------------------*
>
> Best regards,
> Ruilong Huo
>
> On Sat, May 27, 2017 at 7:32 AM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> On Fri, May 26, 2017 at 8:11 AM, Ruilong Huo <rh...@pivotal.io> wrote:
>> > Hi Roman,
>> >
>> > Thanks for your feedback!
>> >
>> > We will merge the license information for the C/C++ components and
>> prepare
>> > LICENSE and NOTICE files accordingly.
>>
>> Great! Let me know when can I review the actual files.
>>
>> > As for JSON in PXF which is incompatible with ASL v2, the fix is to
>> replace
>> > it with some library which is compatible or remove it?
>>
>> Correct. Here's a list of alternative libraries you should start
>> migrating to:
>> https://wiki.debian.org/qa.debian.org/jsonevil
>>
>> There's also http://johnzon.apache.org/
>>
>> And finally:
>>
>> <dependency>
>> <groupId>com.tdunning</groupId>
>> <artifactId>json</artifactId>
>> <version>1.0</version>
>> </dependency>
>>
>> > Furthermore, Hongxu helped to get the license information for Ranger as
>> > well and it turns out that there two dependencies with GPL license
>> which is
>> > also not compatible with ASL v2:
>> >
>> > 1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API that
>> > allows you to stream XML data from and to your application.
>> >
>> > 2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
>> > Contains sources required for runtime processing.
>> >
>> > They are actually directly required by hadoop common and thus is
>> indirectly
>> > required by HAWQ Ranger.
>>
>> I still need to double check it -- but I think those just bring in the
>> APIs which
>> get replaced during the runtime. Will take a deeper look, though.
>>
>> > They are bundled hawq binary during packaging with
>> > maven.
>>
>> Wait. Where are they bundled? I don't see them as part of PXF?
>
>
>
>
>> Thanks,
>> Roman.
>>
>
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
Hi Roman,
The stax-api and jabx-impl are bundled in Ranger, NOT PXF. To be specific,
they are in hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm which is in
apache-hawq-rpm-2.2.0.0-incubating.tar.gz
<https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
.
You can get them with "rpm2cpio
hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm | cpio -div".
The details of the dependency shows that: stax-api and jabx-impl is
dependency of hadoop-common, while hadoop-common is dependency ranger
plugin in hawq.
*$ mvn project-info-reports:dependencies*
*[INFO] Scanning for projects...*
*[INFO]
------------------------------------------------------------------------*
*[INFO] Reactor Build Order:*
*[INFO]*
*[INFO] HAWQ Ranger Plugin*
*[INFO] HAWQ Ranger Admin Plugin*
*[INFO] HAWQ Ranger Service*
*[INFO]*
*[INFO]
------------------------------------------------------------------------*
*[INFO] Building HAWQ Ranger Admin Plugin 2.2.0.0*
*[INFO]
------------------------------------------------------------------------*
*[INFO]*
*[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
ranger-plugin-admin ---*
*[INFO] org.apache.hawq:ranger-plugin-admin:jar:2.2.0.0*
*[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
*[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
*[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
*[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
*[INFO] | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
*[INFO] | | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
*[INFO] | | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
*[INFO] | | | | \- javax.activation:activation:jar:1.1:compile*
*[INFO] ......*
*[INFO]
------------------------------------------------------------------------*
*[INFO] Building HAWQ Ranger Service 2.2.0.0*
*[INFO]
------------------------------------------------------------------------*
*[INFO]*
*[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
ranger-plugin-service ---*
*[INFO] org.apache.hawq:ranger-plugin-service:war:2.2.0.0*
*[INFO] +- org.apache.ranger:ranger-plugins-common:jar:0.6.0:compile*
*[INFO] | +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile*
*[INFO] | | +- com.sun.jersey:jersey-json:jar:1.9:compile*
*[INFO] | | | +- org.codehaus.jettison:jettison:jar:1.1:compile*
*[INFO] | | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile*
*[INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile*
*[INFO] | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile*
*[INFO] | | | \- javax.activation:activation:jar:1.1:compile*
*[INFO] ......*
*[INFO]
------------------------------------------------------------------------*
*[INFO] Reactor Summary:*
*[INFO]*
*[INFO] HAWQ Ranger Plugin ................................. SUCCESS [
0.425 s]*
*[INFO] HAWQ Ranger Admin Plugin ........................... SUCCESS [
0.252 s]*
*[INFO] HAWQ Ranger Service ................................ SUCCESS [
0.099 s]*
*[INFO]
------------------------------------------------------------------------*
*[INFO] BUILD SUCCESS*
*[INFO]
------------------------------------------------------------------------*
*[INFO] Total time: 0.992 s*
*[INFO] Finished at: 2017-05-22T17:24:15+08:00*
*[INFO] Final Memory: 19M/437M*
*[INFO]
------------------------------------------------------------------------*
Best regards,
Ruilong Huo
On Sat, May 27, 2017 at 7:32 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Fri, May 26, 2017 at 8:11 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> > Hi Roman,
> >
> > Thanks for your feedback!
> >
> > We will merge the license information for the C/C++ components and
> prepare
> > LICENSE and NOTICE files accordingly.
>
> Great! Let me know when can I review the actual files.
>
> > As for JSON in PXF which is incompatible with ASL v2, the fix is to
> replace
> > it with some library which is compatible or remove it?
>
> Correct. Here's a list of alternative libraries you should start migrating
> to:
> https://wiki.debian.org/qa.debian.org/jsonevil
>
> There's also http://johnzon.apache.org/
>
> And finally:
>
> <dependency>
> <groupId>com.tdunning</groupId>
> <artifactId>json</artifactId>
> <version>1.0</version>
> </dependency>
>
> > Furthermore, Hongxu helped to get the license information for Ranger as
> > well and it turns out that there two dependencies with GPL license which
> is
> > also not compatible with ASL v2:
> >
> > 1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API that
> > allows you to stream XML data from and to your application.
> >
> > 2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
> > Contains sources required for runtime processing.
> >
> > They are actually directly required by hadoop common and thus is
> indirectly
> > required by HAWQ Ranger.
>
> I still need to double check it -- but I think those just bring in the
> APIs which
> get replaced during the runtime. Will take a deeper look, though.
>
> > They are bundled hawq binary during packaging with
> > maven.
>
> Wait. Where are they bundled? I don't see them as part of PXF?
> Thanks,
> Roman.
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, May 26, 2017 at 8:11 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> Thanks for your feedback!
>
> We will merge the license information for the C/C++ components and prepare
> LICENSE and NOTICE files accordingly.
Great! Let me know when can I review the actual files.
> As for JSON in PXF which is incompatible with ASL v2, the fix is to replace
> it with some library which is compatible or remove it?
Correct. Here's a list of alternative libraries you should start migrating to:
https://wiki.debian.org/qa.debian.org/jsonevil
There's also http://johnzon.apache.org/
And finally:
<dependency>
<groupId>com.tdunning</groupId>
<artifactId>json</artifactId>
<version>1.0</version>
</dependency>
> Furthermore, Hongxu helped to get the license information for Ranger as
> well and it turns out that there two dependencies with GPL license which is
> also not compatible with ASL v2:
>
> 1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API that
> allows you to stream XML data from and to your application.
>
> 2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
> Contains sources required for runtime processing.
>
> They are actually directly required by hadoop common and thus is indirectly
> required by HAWQ Ranger.
I still need to double check it -- but I think those just bring in the
APIs which
get replaced during the runtime. Will take a deeper look, though.
> They are bundled hawq binary during packaging with
> maven.
Wait. Where are they bundled? I don't see them as part of PXF?
Thanks,
Roman.
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
Hi Roman,
Thanks for your feedback!
We will merge the license information for the C/C++ components and prepare
LICENSE and NOTICE files accordingly.
As for JSON in PXF which is incompatible with ASL v2, the fix is to replace
it with some library which is compatible or remove it?
Furthermore, Hongxu helped to get the license information for Ranger as
well and it turns out that there two dependencies with GPL license which is
also not compatible with ASL v2:
1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API that
allows you to stream XML data from and to your application.
2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
Contains sources required for runtime processing.
They are actually directly required by hadoop common and thus is indirectly
required by HAWQ Ranger. They are bundled hawq binary during packaging with
maven. Further check in hadoop binary shows that they are bundled as well.
However, the LICENSE in hadoop binary does not include them. Would you
please shed some light on how to handle this case? Thanks.
Best regards,
Ruilong Huo
On Fri, May 26, 2017 at 10:11 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Tue, May 23, 2017 at 12:39 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> > Thanks Lei and Roman for the comments. Keeping the LICENSE and NOTICE
> files
> > separated for each hawq rpm package makes it clear to understand and
> > minimum maintenance effort.
> >
> > The DISCLAIMER is common for hawq components. However, we have separate
> > binary packages for different components, such hawq core, pxf, and
> ranger,
> > which means users might download and install them separately.
> > So, I would prefer that we have separate DISCLAIMER file for each of the
> > hawq rpm package.
> >
> > For now, we have identified the license information for hawq dependencies
> > and proposed the process to merge that information to LICENSE and NOTICE
> > files for hawq components. Can you review that and give your feedback
> > before we prepare these files for further review?
>
> I took a look at the spreadsheet and I think you're on exactly the right
> track.
> For C/C++ components I trust your evaluation. As for PXF -- I'd like to
> take
> a look at how they compose their JARs myself.
>
> Ed and I already identified one issues with PXF that would have to be
> fixed:
> json can't be used because of the "do no evil" license.
>
> > Also, can you please elaborate on the license management plugin and
> > documentation for them? Thanks.
>
> These are mostly useful for Java projects but here's what I had in mind:
> https://github.com/hierynomus/license-gradle-plugin
> http://www.mojohaus.org/license-maven-plugin/
> https://github.com/pivotal/LicenseFinder
>
> Thanks,
> Roman.
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, May 23, 2017 at 12:39 AM, Ruilong Huo <rh...@pivotal.io> wrote:
> Thanks Lei and Roman for the comments. Keeping the LICENSE and NOTICE files
> separated for each hawq rpm package makes it clear to understand and
> minimum maintenance effort.
>
> The DISCLAIMER is common for hawq components. However, we have separate
> binary packages for different components, such hawq core, pxf, and ranger,
> which means users might download and install them separately.
> So, I would prefer that we have separate DISCLAIMER file for each of the
> hawq rpm package.
>
> For now, we have identified the license information for hawq dependencies
> and proposed the process to merge that information to LICENSE and NOTICE
> files for hawq components. Can you review that and give your feedback
> before we prepare these files for further review?
I took a look at the spreadsheet and I think you're on exactly the right track.
For C/C++ components I trust your evaluation. As for PXF -- I'd like to take
a look at how they compose their JARs myself.
Ed and I already identified one issues with PXF that would have to be fixed:
json can't be used because of the "do no evil" license.
> Also, can you please elaborate on the license management plugin and
> documentation for them? Thanks.
These are mostly useful for Java projects but here's what I had in mind:
https://github.com/hierynomus/license-gradle-plugin
http://www.mojohaus.org/license-maven-plugin/
https://github.com/pivotal/LicenseFinder
Thanks,
Roman.
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
Thanks Lei and Roman for the comments. Keeping the LICENSE and NOTICE files
separated for each hawq rpm package makes it clear to understand and
minimum maintenance effort.
The DISCLAIMER is common for hawq components. However, we have separate
binary packages for different components, such hawq core, pxf, and ranger,
which means users might download and install them separately.
So, I would prefer that we have separate DISCLAIMER file for each of the
hawq rpm package.
For now, we have identified the license information for hawq dependencies
and proposed the process to merge that information to LICENSE and NOTICE
files for hawq components. Can you review that and give your feedback
before we prepare these files for further review?
Also, can you please elaborate on the license management plugin and
documentation for them? Thanks.
Best regards,
Ruilong Huo
On Tue, May 23, 2017 at 12:46 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Hi!
>
> sorry for the belated reply. A couple of points:
> 0. do you have the binary LICENSE and NOTICE files available some place
> so I can review them before we make a decision on where they need to go?
>
> 1. personally I'd prefer option #2 but truth be told I don't really
> understand why
> would you have a separate copy of DISCLAIMER -- that is common between
> everything and can be taken from the top level
>
> 2. for Java binaries (such as PXF) it may be much more convenient to use
> one of the license management plugins available rather than to try and
> manage
> it manually. Remember -- you'd have to make sure appropriate
> licensing statement
> ends up in jar files.
>
> Thanks,
> Roman.
>
> On Sun, May 21, 2017 at 7:15 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> > Hi Roman,
> >
> > Please let us know if you get a chance to review this. Or someone else
> who
> > can help on this? Thanks.
> >
> > Best regards,
> > Ruilong Huo
> >
> > On Mon, May 15, 2017 at 3:12 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> >
> >> Hi Roman,
> >>
> >> Currently I am preparing LICENSE, NOTICE, and DISCLAIMER files for
> Apache
> >> HAWQ 2.2.0.0-incubating rpm binary release. The components of the binary
> >> package
> >> <https://dist.apache.org/repos/dist/dev/incubator/hawq/
> 2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> >> are as below:
> >>
> >> *> tar -xzvf apache-hawq-rpm-2.2.0.0-incubating.tar.gz; tree
> >> hawq_rpm_packages*
> >> hawq_rpm_packages
> >> ├── apache-hawq-2.2.0.0-el7.x86_64.rpm
> >> ├── apache-tomcat-7.0.62-el6.noarch.rpm
> >> ├── hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm
> >> ├── pxf-3.2.1.0-1.el6.noarch.rpm
> >> ├── pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> >> ├── pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> >> ├── pxf-hive-3.2.1.0-1.el6.noarch.rpm
> >> ├── pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> >> ├── pxf-json-3.2.1.0-1.el6.noarch.rpm
> >> └── pxf-service-3.2.1.0-1.el6.noarch.rpm
> >>
> >> Given the LICENSE, NOTICE, and DISCLAIMER for Apache HAWQ source in top
> >> directory:
> >>
> >> *> tree incubator-hawq/*
> >> incubator-hawq/
> >> ├── DISCLAIMER
> >> ├── LICENSE
> >> └── NOTICE
> >>
> >> We plan to put LICENSE, NOTICE, and DISCLAIMER for binary release in a
> >> dedicated directory named dist which under top directory. Then these
> files
> >> will be copied to the rpm packages in packaging stage.
> >>
> >> Here are two options for the layout of the LICENSE, NOTICE, and
> DISCLAIMER
> >> for the components:
> >>
> >> *Option 1: Combine the licenses of all the components into one LICENSE,
> >> NOTICE, and DISCLAIMER respectively. For example:*
> >>
> >> *> cd $APACHE_HAWQ_TOP_DIR; tree dist*
> >> dist
> >> ├── DISCLAIMER
> >> ├── LICENSE
> >> └── NOTICE
> >>
> >> *Option 2: Keep the separated LICENSE, NOTICE, and DISCLAIMER for each
> of
> >> the components. For example:*
> >>
> >> *> cd $APACHE_HAWQ_TOP_DIR; tree dist/*
> >> dist/
> >> ├── hawq
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf-hbase
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf-hdfs
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf-hive
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf-jdbc
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf-json
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── pxf-service
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> ├── ranger-plugin
> >> │ ├── DISCLAIMER
> >> │ ├── LICENSE
> >> │ └── NOTICE
> >> └── tomcat
> >> ├── DISCLAIMER
> >> ├── LICENSE
> >> └── NOTICE
> >>
> >> For option 1, it is easier to maintain the LICENSE, NOTICE, and
> DISCLAIMER
> >> files. However, it contains all the licenses for all the components.
> Thus
> >> it is hard to identify which component contains what licenses.
> >>
> >> For option 2, it needs extra maintenance effort. But, it is clear that
> >> what are the licenses for each of the components.
> >>
> >> Would you please share you comments and let us know which is better?
> >> Thanks.
> >>
> >> Best regards,
> >> Ruilong Huo
> >>
>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Hi!
sorry for the belated reply. A couple of points:
0. do you have the binary LICENSE and NOTICE files available some place
so I can review them before we make a decision on where they need to go?
1. personally I'd prefer option #2 but truth be told I don't really
understand why
would you have a separate copy of DISCLAIMER -- that is common between
everything and can be taken from the top level
2. for Java binaries (such as PXF) it may be much more convenient to use
one of the license management plugins available rather than to try and manage
it manually. Remember -- you'd have to make sure appropriate
licensing statement
ends up in jar files.
Thanks,
Roman.
On Sun, May 21, 2017 at 7:15 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> Please let us know if you get a chance to review this. Or someone else who
> can help on this? Thanks.
>
> Best regards,
> Ruilong Huo
>
> On Mon, May 15, 2017 at 3:12 PM, Ruilong Huo <rh...@pivotal.io> wrote:
>
>> Hi Roman,
>>
>> Currently I am preparing LICENSE, NOTICE, and DISCLAIMER files for Apache
>> HAWQ 2.2.0.0-incubating rpm binary release. The components of the binary
>> package
>> <https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
>> are as below:
>>
>> *> tar -xzvf apache-hawq-rpm-2.2.0.0-incubating.tar.gz; tree
>> hawq_rpm_packages*
>> hawq_rpm_packages
>> ├── apache-hawq-2.2.0.0-el7.x86_64.rpm
>> ├── apache-tomcat-7.0.62-el6.noarch.rpm
>> ├── hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm
>> ├── pxf-3.2.1.0-1.el6.noarch.rpm
>> ├── pxf-hbase-3.2.1.0-1.el6.noarch.rpm
>> ├── pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
>> ├── pxf-hive-3.2.1.0-1.el6.noarch.rpm
>> ├── pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
>> ├── pxf-json-3.2.1.0-1.el6.noarch.rpm
>> └── pxf-service-3.2.1.0-1.el6.noarch.rpm
>>
>> Given the LICENSE, NOTICE, and DISCLAIMER for Apache HAWQ source in top
>> directory:
>>
>> *> tree incubator-hawq/*
>> incubator-hawq/
>> ├── DISCLAIMER
>> ├── LICENSE
>> └── NOTICE
>>
>> We plan to put LICENSE, NOTICE, and DISCLAIMER for binary release in a
>> dedicated directory named dist which under top directory. Then these files
>> will be copied to the rpm packages in packaging stage.
>>
>> Here are two options for the layout of the LICENSE, NOTICE, and DISCLAIMER
>> for the components:
>>
>> *Option 1: Combine the licenses of all the components into one LICENSE,
>> NOTICE, and DISCLAIMER respectively. For example:*
>>
>> *> cd $APACHE_HAWQ_TOP_DIR; tree dist*
>> dist
>> ├── DISCLAIMER
>> ├── LICENSE
>> └── NOTICE
>>
>> *Option 2: Keep the separated LICENSE, NOTICE, and DISCLAIMER for each of
>> the components. For example:*
>>
>> *> cd $APACHE_HAWQ_TOP_DIR; tree dist/*
>> dist/
>> ├── hawq
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf-hbase
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf-hdfs
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf-hive
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf-jdbc
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf-json
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── pxf-service
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> ├── ranger-plugin
>> │ ├── DISCLAIMER
>> │ ├── LICENSE
>> │ └── NOTICE
>> └── tomcat
>> ├── DISCLAIMER
>> ├── LICENSE
>> └── NOTICE
>>
>> For option 1, it is easier to maintain the LICENSE, NOTICE, and DISCLAIMER
>> files. However, it contains all the licenses for all the components. Thus
>> it is hard to identify which component contains what licenses.
>>
>> For option 2, it needs extra maintenance effort. But, it is clear that
>> what are the licenses for each of the components.
>>
>> Would you please share you comments and let us know which is better?
>> Thanks.
>>
>> Best regards,
>> Ruilong Huo
>>
Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
2.2.0.0-incubating rpm binary release
Posted by Ruilong Huo <rh...@pivotal.io>.
Hi Roman,
Please let us know if you get a chance to review this. Or someone else who
can help on this? Thanks.
Best regards,
Ruilong Huo
On Mon, May 15, 2017 at 3:12 PM, Ruilong Huo <rh...@pivotal.io> wrote:
> Hi Roman,
>
> Currently I am preparing LICENSE, NOTICE, and DISCLAIMER files for Apache
> HAWQ 2.2.0.0-incubating rpm binary release. The components of the binary
> package
> <https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> are as below:
>
> *> tar -xzvf apache-hawq-rpm-2.2.0.0-incubating.tar.gz; tree
> hawq_rpm_packages*
> hawq_rpm_packages
> ├── apache-hawq-2.2.0.0-el7.x86_64.rpm
> ├── apache-tomcat-7.0.62-el6.noarch.rpm
> ├── hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm
> ├── pxf-3.2.1.0-1.el6.noarch.rpm
> ├── pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> ├── pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> ├── pxf-hive-3.2.1.0-1.el6.noarch.rpm
> ├── pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> ├── pxf-json-3.2.1.0-1.el6.noarch.rpm
> └── pxf-service-3.2.1.0-1.el6.noarch.rpm
>
> Given the LICENSE, NOTICE, and DISCLAIMER for Apache HAWQ source in top
> directory:
>
> *> tree incubator-hawq/*
> incubator-hawq/
> ├── DISCLAIMER
> ├── LICENSE
> └── NOTICE
>
> We plan to put LICENSE, NOTICE, and DISCLAIMER for binary release in a
> dedicated directory named dist which under top directory. Then these files
> will be copied to the rpm packages in packaging stage.
>
> Here are two options for the layout of the LICENSE, NOTICE, and DISCLAIMER
> for the components:
>
> *Option 1: Combine the licenses of all the components into one LICENSE,
> NOTICE, and DISCLAIMER respectively. For example:*
>
> *> cd $APACHE_HAWQ_TOP_DIR; tree dist*
> dist
> ├── DISCLAIMER
> ├── LICENSE
> └── NOTICE
>
> *Option 2: Keep the separated LICENSE, NOTICE, and DISCLAIMER for each of
> the components. For example:*
>
> *> cd $APACHE_HAWQ_TOP_DIR; tree dist/*
> dist/
> ├── hawq
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf-hbase
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf-hdfs
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf-hive
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf-jdbc
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf-json
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── pxf-service
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> ├── ranger-plugin
> │ ├── DISCLAIMER
> │ ├── LICENSE
> │ └── NOTICE
> └── tomcat
> ├── DISCLAIMER
> ├── LICENSE
> └── NOTICE
>
> For option 1, it is easier to maintain the LICENSE, NOTICE, and DISCLAIMER
> files. However, it contains all the licenses for all the components. Thus
> it is hard to identify which component contains what licenses.
>
> For option 2, it needs extra maintenance effort. But, it is clear that
> what are the licenses for each of the components.
>
> Would you please share you comments and let us know which is better?
> Thanks.
>
> Best regards,
> Ruilong Huo
>