@Sim - Fair enough, I’ll refer the questions.  First, though I’m going through 
the archives on legal-discuss@ to see if there’s already been a discussion.  As 
with many things, there seems to be much opinion, but little policy.  For 
example, in 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201305.mbox/%3CED615624-F77B-487F-BA82-F8BD0E50CA46%40gmail.com%3E
 Sam Ruby says he thinks projects shouldn’t but binaries into svn, however, at 
the same time I asked the question over on general@incubator.a.o, and it was 
pointed out that projects like Apache Open Office and Apache Cassandra have 
many binaries in svn.

At the same time, I’ll mention that I did some experimenting last night with 
Apache Ivy (http://ant.apache.org/ivy), and it seems almost trivially easy to 
get dependencies at build time, so long as they’re in Maven Central.  I’ll post 
a patch for the 2.2 branch for people to take a look at (probably on Monday as 
I’m a little busy in the next few days).   It’s about 20 lines added to 
“build.xml" and about a 20-line “ivy.xml” file.  So I wonder, is there a reason 
we’d want to keep jars in svn if they weren’t strictly necessary?

By the way, I realize in re-reading it that my initial comments may have seemed 
heavy-handed, and I’m sorry about that.  I’m really just concerned that 
consensus seems to be converging (at least in the Incubator, which is often the 
de-facto policy body) on “no jars in svn, download them at build time”, and 
we’re not currently doing that.

Regards,

Greg Trasuk.

On Dec 19, 2013, at 7:12 AM, Peter <j...@zeus.net.au> wrote:

> No, we can't distribute external binaries either.  The binary has to be the 
> compiled version of the source.
> 
> 
> ----- Original message -----
>> I dont think the pathnames constitute a whole lot of difference in 
>> copyright terms. I think this issue revolves around having no binary 
>> products of anyone in the source distribution (the source release).
>> 
>> I've no opinion yet on if 'tool' jars belong in a binary distribution.
>> 
>> Gr. Simon
>> 
>> On 19-12-13 12:10, Peter wrote:
>>> Looking at the last paragraph in Sam's email he goes on to say we can
>>> have jar files in svn for build tools etc, but not in our open source
>>> product trees.
>>> 
>>> In that case the easiest temporary solution would be to move them
>>> into a designated directory outside of our product tree, then we can
>>> have ant retrieve them as needed for jenkins tests until we work out
>>> a more permanent solution.
>>> 
>>> Cheers,
>>> 
>>> Peter.
>>> 
>>> 
>> 
>> 
>> -- 
>> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
>> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
> 

Reply via email to