maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse McConnell <>
Subject Re: A legal-ish question
Date Fri, 11 Jun 2010 14:27:07 GMT
imo where ever you drop the code just make it very clear where it came
from, a link to this thread might not hurt to add as well...point
being as others have said it should be perfectly fine for code @ the
ASF but these sorts of things have a way of rearing their ugly head
years down the road and having any sort of documented history of the
code helps immensely.

as painful as it can be to do, this sort of IP tracking is critically
important within code like this

being more involved in the IP process @ eclipse now, I can testify
that Jason is completely correct on the level of detail for IP
validation within Eclipse, its staggering at times.


jesse mcconnell

On Fri, Jun 11, 2010 at 09:16, Kristian Rosenvold
<> wrote:
> fr., 11.06.2010 kl. 06.35 -0700, skrev Jason van Zyl:
>> On Jun 10, 2010, at 11:27 PM, Kristian Rosenvold wrote:
>> > I have a memoizer
>> > ( that
>> > I'd like to include "somewhere" in our code base. It's like 30 lines of
>> > code or so.
>> >
>> > Ï've seen this snippet of code (or extremely minor permutations of it)
>> > appear a number of places, under various lisence headers, for instance:
>> >
>> >
>> >
>> >
>> > What's the appropriate thing to do IP-wise wrt including such a piece of
>> > code ? The specific implementation I've linked to appears on page 108 of
>> > the "Java Concurrency in practice" book.
>> >
>> It's fine, bringing anything up on the legal lists here is a waste of time.
>>  will check the code with the folks at Eclipse and let you know if there is any
>> Apache has no IP checking system at all so it's honestly generally useless asking
anyone here.
>> Eclipse has a real IP clearance mechanism with real lawyers, with a real set of tools
>> validation using humans, Black Duck and Palimida. If you've found a public domain
>> then you're fine, but I'll ask the Eclipse IP team.
> Sebb identified the piece of code as "public domain" via the official
> website of the book; I was looking in the hardcopy and couldn't find it
> in the printed book. So much for dead trees.
> Now the link Brett sent doesn't explicitly name "Public domain" as a
> "license" with compatibility constraints, but it seems implied in the
> section on Doug Lea's concurrent library:
> Kristian
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message