[
https://issues.apache.org/jira/browse/RIVER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860363#comment-13860363
]
Greg Trasuk commented on RIVER-432:
-----------------------------------
It appears that I was wrong. Apache policy does not forbid jars in svn. The
arguments are complicated, as reflected in this discussion:
http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3C01B04CC4-95B8-4A39-BC16-04BAA4269B65%40stratuscom.com%3E
I still suggest that given how easy it is to use Apache Ivy to retrieve
dependency jars at build time, we should try to move all branches towards this
technique, as the patch above does for the 2.2 branch.
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
> Attachments: 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)
