batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject Re: Question on LICENSE(s) for certain modules
Date Thu, 25 Dec 2014 23:29:36 GMT
But all that should not affect the licenses of BatchEE itself!
So we should imo really remove those lines.


LieGrue,
strub





> On Tuesday, 23 December 2014, 15:45, Romain Manni-Bucau <rmannibucau@gmail.com>
wrote:
> > Hi Scott,
> 
> I guess it comes from openejb optional dependency which has all theses
> project as dependency - no more sure but I think we bundle openejb in
> one of our assemblies.
> 
> 
> 
> Romain Manni-Bucau
> @rmannibucau
> http://www.tomitribe.com
> http://rmannibucau.wordpress.com
> https://github.com/rmannibucau
> 
> 
> 
> 2014-12-23 15:17 GMT+01:00 Scott Kurz <skurz3@gmail.com>:
>>  Hi,
>> 
>>  I noticed in looking over the set of LICENSE files in the source tree.
>> 
>>  The file:
>>     ./tools/cli/src/main/resources/META-INF/LICENSE
>>  contains a normal ASL 2 license followed by a bunch of other included
>>  licenses.
>> 
>>  E.g. JAnsi, HSQLDB, Javassist, and more....
>> 
>>  Trying to understand how to map these licenses onto code.
>> 
>>  Is the intention to show that these extra licenses apply specifically to
>>  the tools/cli module (but not the other modules)?
>> 
>>  Since the file:
>>  ./tools/cli/src/main/resources/META-INF/NOTICE
>>  references project:
>>   https://github.com/airlift/airline/
>> 
>>  I had thought maybe it was this project that through its license had
>>  dragged in all these other references.   In looking at this project's
>>  license in GitHub, though, that doesn't seem to be the case.
>> 
>>  I also couldn't easily map these extra licenses to additional 
> references in
>>  the POM, (though maybe I didn't look hard enough).
>> 
>>  Would anyone be able to help me better understand this module's 
> licensing?
>> 
>>  I'd greatly appreciate it.
>> 
>>  ...
>> 
>>  Other than this one module, the rest of the modules seem to all be licensed
>>  under ASL 2, with the exception of a reference to the JUNG license in the
>>  tools/maven-plugin.   In this case the POM seems to confirm it is only this
>>  one module with a reference to JUNG, which fits with the licensing for this
>>  module.
>> 
>>  Thank you,
>>  Scott Kurz
> 

Mime
View raw message