[
https://issues.apache.org/jira/browse/RIVER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Trasuk closed RIVER-432.
-----------------------------
Resolution: Won't Fix
Vote thread on
http://mail-archives.apache.org/mod_mbox/river-dev/201402.mbox/%3C7DC70848-B027-43E3-922F-A4CAF27CED04%40stratuscom.com%3E
rejected the patches.
> 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
> Attachments: river-2_2_remove_jars.diff, river-2_2_remove_jars.diff
>
>
> 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.5#6160)