[
https://issues.apache.org/jira/browse/PHOENIX-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382397#comment-15382397
]
Josh Elser commented on PHOENIX-3091:
-------------------------------------
I was talking to experts [~joewitt] and [~billie.rinaldi] this morning (thanks
to you both!) on what really needs to be addressed here since I was a bit
confused on how to handle a tarball of JAR files.
What I'm used to seeing is that projects will deploy a staged repository to the
ASF's nexus server (https://repository.apache.org). Each of these JAR files
constitutes a binary release on its own (a user can download a JAR via
Maven/Ivy/etc). Since Phoenix is only deploying a tarball which contains all of
the jars, it makes the short-term a bit easier, actually. Only the tarball
needs to have the appropriate L&N files -- we can punt on each jar. In a
perfect world where all of our dependencies have appropriate L&N files, the
Maven shade plugin will actually do a fair bit of the work for us (which is
nice).
I believe all we really need to focus on for the immediate is corralling all of
the projects which are bundled within the JARs contained in the binary release
tarball and ensuring the L&N are accurate. Down the road, if/when we want to
deploy these artifacts to central for users to easily access, we can validate
the L&N for each JAR.
> Licensing issues with binary release
> ------------------------------------
>
> Key: PHOENIX-3091
> URL: https://issues.apache.org/jira/browse/PHOENIX-3091
> Project: Phoenix
> Issue Type: Task
> Reporter: Josh Elser
>
> Umbrella issue to track fixes to the binary release for Apache Phoenix.
> Original thread:
> https://lists.apache.org/thread.html/f887f8213a81881df8e25cf63ab076b019fd46113fb25f8c8a085412@%3Cdev.phoenix.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
