[
https://issues.apache.org/jira/browse/RIVER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852317#comment-13852317
]
Greg Trasuk commented on RIVER-432:
-----------------------------------
The topic came up in regards to a release of Apache Spark Incubating. I quote
Marvin Humphrey from that list
(http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3CCAAS6%3D7iQSKTgNdO-0Qyd3T9--%2B%2BHQFEmhJi7CHoByqvQvp9_bg%40mail.gmail.com%3E)
Please read these messages from ASF Board member Roy Fielding:
http://s.apache.org/roy-binary-deps-0
http://s.apache.org/roy-binary-deps-1
http://s.apache.org/roy-binary-deps-2
http://s.apache.org/roy-binary-deps-3
This has to be fixed. If some TLP PMCs have not been made aware that binary
dependencies may not be bundled in source releases, the Incubator must not
compound the problem by failing to educate current podlings.
Cheers,
Greg.
> Jar files in svn and src distributions
> --------------------------------------
>
> Key: RIVER-432
> URL: https://issues.apache.org/jira/browse/RIVER-432
> Project: River
> Issue Type: Bug
> Reporter: Greg Trasuk
>
> Recent traffic on the incubator lists has pointed out that including jar
> files for dependencies in the subversion repository and the source
> distributions is against Apache policy.
> In River, the following libraries appear in the Subversion repository and the
> source distributions (these are from trunk, a smaller set appear in the 2.2
> branch):
> animal-sniffer
> asm
> bouncy-castle
> dnsjava
> high-scale-lib
> rc-libs
> velocity
> They all have to go. What are we using them for? As I understand it, we
> were going to remove the VelocityConfigurationBuilder, so that's not a
> problem. Some of the others are available from Maven Central, so we can get
> them at build time using Ivy or another build tool. Which ones are actually
> required? And where did they come from?
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
