[ 
https://issues.apache.org/jira/browse/RIVER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Trasuk updated RIVER-432:
------------------------------

    Attachment: river-2_2_remove_jars.diff

The attached patch for the 2.2 branch does the following:
- removes the 'asm' directory and 'tests/lib' directories which currently 
contain the asm library, mockito, and junit jars.
- Modifies 'build.xml', 'common.xml', and adds 'ivy.xml' so that the Apache Ivy 
ant plugin is downloaded at build time, and then used to retrieve the libraries 
mentioned above from Maven Central.  This removes the need to have the jar 
files in svn.
- Removes (as per discussion 
http://mail-archives.apache.org/mod_mbox/river-dev/201211.mbox/%3C509B99E3.6080800%40qcg.nl%3E)
 the VelocityConfigBuilder, and associated Velocity jars.  Note that the 
'extras' folder is not present in the 2.2 branch, so Sim's last comments in the 
thread do not apply.

> 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)

Reply via email to