Keep in mind for testing and development purposes, there are times when we'll need to compile a jar and store it on svn for hudson. Eg: a cvs branch of ASM is required before we can build on JDK8, a task I'd like to do so shortly to ensure we can raise any issues with OpenJDK. This isn't likely to happen too often, but we need to retain the ability to do so if necessary.
Regards, Peter. ----- Original message ----- > > [ > https://issues.apache.org/jira/browse/RIVER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870763#comment-13870763 > ] > > Dennis Reedy commented on RIVER-432: > ------------------------------------ > > I'm all in favor of using Ivy and removing the jars from svn and using > Ivy. > > > 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)
