[
https://issues.apache.org/jira/browse/RIVER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852503#comment-13852503
]
Peter Firmstone commented on RIVER-432:
---------------------------------------
If they're in our source distribution jar, they shouldn't be, we need to fix
the build script. They're in svn so Jenkins will build properly.
>From memory (there was a discussion on the mail list while River was an
>incubator podling, will try to locate it for you when I get time) so long as
>they're apache license compliant, it's ok for them to be on svn, if they use
>an incompatible license, they need to be installed on Jenkins nodes as a
>platform dependency, this is the case with jtreg, which is why we haven't been
>running the regression tests on Jenkins.
Shortly, I'm going to need to build asm libs from objectweb's svn server, so we
can test on Java 8, our build script won't run without an existing asm released
version on Java 8.
These are necessary for development, but for obvious reasons shouldn't be
included with source or binary releases.
Longer term if this is an issue for people, we could look for ways to download
the files on demand or create build dependencies, eg for asm (that means
download and build asm from object web's svn on Jenkins). But with my present
workload that wouldn't be one of my top priorities.
> 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)
