[
https://issues.apache.org/jira/browse/MRQL-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782423#comment-13782423
]
Leonidas Fegaras commented on MRQL-19:
--------------------------------------
The following MRQL-q9-3.patch changes the source structure so that maven
generates 5 independent jars with no overlapping class:
1) mrql-gen (the Gen tool)
2) mrql-core (the core code used by all evaluation engines)
3) mrql-mr (the code for hadoop map-reduce)
4) mrql-bsp (the code for Hama BSP)
5) mrql-spark (the code for Spark)
I think we can now release the binary distribution along with the source
because all L&N issues have been resolved (no 3rd party libraries) and there is
code repetition.
If these changes are OK, I will apply the patch and I will stage the source
distribution for voting at the MRQL dev list.
> 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
>
> Attachments: MRQL-19.2.patch, MRQL-19-3.patch, MRQL-19.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
