[
https://issues.apache.org/jira/browse/CASSANDRA-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841936#action_12841936
]
Eric Evans commented on CASSANDRA-850:
--------------------------------------
> Isn't the point of a binary release tarball that it should work with minimal
> effort out of the box?
The added effort basically boils down to invoking `ant ivy-retrieve' no?
> Surely the overhead of maintaining the notice file is a tiny bit of extra
> effort for a small group of developers and of a major benefit to a large
> group of users?
I think "tedious" is a better adjective than "tiny". Also, despite the very
best of intentions, it wasn't being kept up properly (which is a pretty common
outcome of tedious manual tasks).
We traded:
* manual dependency management
* the requirement to document license and attribution
* license incompatibility issues (caused by redistribution)
For:
* requiring ant to be installed (which doesn't seem to be too onerous)
* requiring network connectivity
* invoking `ant ivy-retrieve'
I'm not opposed to returning to the past practice of embedding all of the jars,
especially if someone is stepping up to do a better job of maintaining this,
but I think the changeset needs to revert Ivy, and include the jars and the
necessary changes to NOTICE and LICENSE .
> Ant release target doesn't include all jars in tarball
> ------------------------------------------------------
>
> Key: CASSANDRA-850
> URL: https://issues.apache.org/jira/browse/CASSANDRA-850
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Attachments: CASSANDRA-850.patch
>
>
> The ant release target doesn't create a complete tarball, the jars in
> build/lib/jars are not included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
