[
https://issues.apache.org/jira/browse/MRQL-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780878#comment-13780878
]
Leonidas Fegaras commented on MRQL-19:
--------------------------------------
I created a patch, which is attached next. I did the following changes:
1) Changed the name MRQL in POMs to Apache MRQL.
2) Changed the gen package to mrql-gen.
3) POM assembly creates 1 source and 3 different binary distributions:
mrql-dist-*-bin-mr.tar.gz, mrql-dist-*-bin-bsp.tar.gz, and
mrql-dist-*-bin-spark.tar.gz, for Hadoop, Hama, and Spark.
4) I removed all 3rd party references/licenses from the LICENSE and NOTICE for
the source distribution.
5) The binary distributions have now their own LICENSE and NOTICE, which
include license info for JLine and CUP runtime libraries. These are in the
dist/bin-info directory and are copied to the top directory during the binary
assembly.
I will stage for vote ONLY the source distribution. I think if we include the
binary distribution, we will have issues again. After the source distro is
approved by IPMC, I will put the binaries in some non-Apache web site.
Please vote +1 if you approve these changes.
If they are OK, I will apply the patch and I will stage the source distribution
for voting at the MRQL dev list first on Monday morning.
> Fix license issues to prepare a new release candidate
> -----------------------------------------------------
>
> Key: MRQL-19
> URL: https://issues.apache.org/jira/browse/MRQL-19
> Project: MRQL
> Issue Type: Task
> Affects Versions: 0.9.0
> Reporter: Leonidas Fegaras
> Assignee: Leonidas Fegaras
> Fix For: 0.9.0
>
>
> We need to address the license issues reported by sebb before we stage a new
> release candidate for vote.
> Here are sebb's emails:
> http://markmail.org/message/z66lnr5q4u24rwal
> http://markmail.org/message/k7zvajrn3hnla3ve
> My opinion is that we should not release any binary artifacts. We release
> only source. The problem is that the generated jars must bundle all the
> dependencies (which are the runtime JLine and CUP libraries) in order to run
> as single jars on Hadoop or Hama. This means that we have to repeat the
> JLine/CUP classes in the MRQL jars, which is something sebb doesn't like.
> Also, if we release binaries, the license files of the source distribution
> must be different from that of the binary since we don't use JLine/CUP source
> code.
> What do you think?
> All the other issues are easy to fix.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
