RFR - JDK-8149776 - BSD license for jimage code

[Mario Torre]

Hi Alan,

I wanted to comment on that too, but Andrew beat me. Anyway this
answer doesn't really tell anything useful and I would like some more context.

I understand that Oracle *may* have the rights to change licensing at
any time due to the OCA (although my assumption is more that Oracle
has the right to dual license the code, not arbitrarily change it),
but any change should be communicated in advance and perhaps
discussed. I actually expect such change to be discussed by the legal
body that drives OpenJDK development, not something trivially done
with a secret bug report.

In this case we are relaxing the licensing restriction may seem a
generous and innocent change, and we could be fine with that, but
again I still question the method used, an after the fact commit
referencing a non accessible bug.

On a side note, the GPL+Exception allows linkage of closed source, so
unless one wants to modify the actual code, I don't understand why
this change is needed at all.

I'm worried that this makes a dangerous precedent.

Cheers,
Mario

2016-02-15 11:51 GMT+01:00 Alan Bateman <Alan.Bateman at oracle.com>:
>
> On 15/02/2016 09:29, Andrew Dinn wrote:
>>
>> :
>>
>> Can someone provide some context to explain why this is being done?
>>
>>
> This is to allow the code be used by VM implementations that are allergic to
> GPL or GPL + "Classpath" exception, nothing more.
>
> -Alan.



-- 
pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF

Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens
Proud GNU Classpath developer: http://www.classpath.org/
OpenJDK: http://openjdk.java.net/projects/caciocavallo/

Please, support open standards:
http://endsoftpatents.org/