Forum: JRuby License issue when shipping together(Re: [jruby-user] JRuby invocation through JSR223 aprox 17x fast

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Yoko H. (Guest)
on 2008-11-19 17:27
(Received via mailing list)
Hi,

I asked at scripting.dev.java.net and researched about a license issue
of JSR 223 engine for shipping together with JRuby. JSR 223 engines
released at java.net have BSD style license with Sun's copyright while
JRuby has triple, CPL, GPL, and LGPL license. The point is whether
Sun's copyright is regarded as "advertising" or not in terms of GPL.
If it is not, shiping together has no problem. JSR 223 engine would be
able to keep its license without any modification. If it is, we need
to work on licensing to fit in. For example, asking Sun for permission
to modify (or delete?) copyright.

Do you think the license below is advertising?

LISENSE.TXT:
Copyright (c) 2006, Sun Microsystems, Inc.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

 - Redistributions of source code must retain the above copyright
notice, this
   list of conditions and the following disclaimer.

 - Redistributions in binary form must reproduce the above copyright
notice,
   this list of conditions and the following disclaimer in the
documentation
   and/or other materials provided with the distribution.

 - Neither the name of the Sun Microsystems, Inc. nor the names of
   contributors may be used to endorse or promote products derived from
this
   software without specific prior written permission.


Copyrgiht in each source code:

 * Copyright 2006 Sun Microsystems, Inc. All rights reserved.
 * Use is subject to license terms.
 *
 * Redistribution and use in source and binary forms, with or without
modification,are
 * permitted provided that the following conditions are met:
Redistributions of source code
 * must retain the above copyright notice, this list of conditions and
the following disclaimer.
 * Redistributions in binary form must reproduce the above copyright
notice, this list of
 * conditions and the following disclaimer in the documentation and/or
other materials
 * provided with the distribution. Neither the name of the Sun
Microsystems nor the names of
 * is contributors may be used to endorse or promote products derived
from this software
 * without specific prior written permission.

-Yoko

On Mon, Nov 17, 2008 at 10:54 AM, Yoko H. <removed_email_address@domain.invalid> 
wrote:
>> into JRuby proper and just start shipping it. It would allow us to make
> Besides, I think JRuby engine should have refactoring by using JRuby's
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Thomas E Enebo (Guest)
on 2008-11-19 18:47
(Received via mailing list)
I do not think this could be released under either GPL or LGPL since
the copyright adds additional licensing conditions.

-Tom

On Wed, Nov 19, 2008 at 10:24 AM, Yoko H. <removed_email_address@domain.invalid> 
wrote:
> to modify (or delete?) copyright.
>  - Redistributions of source code must retain the above copyright notice, this
>
> the following disclaimer.
> -Yoko
>>>
>> I think reimplementation doesn't have any obstacle since some of
>>> ---------------------------------------------------------------------
>
>    http://xircles.codehaus.org/manage_email
>
>
>



--
Blog: http://www.bloglines.com/blog/ThomasEEnebo
Email: removed_email_address@domain.invalid , 
removed_email_address@domain.invalid

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
This topic is locked and can not be replied to.