Openj9: Clarify the license / legal status (relative to Oracle).

Created on 3 Jun 2018  Â·  10Comments  Â·  Source: eclipse/openj9

This is an ask for the documentation. Should be easy (I hope).

What is the legal status of OpenJ9 relative to Oracle? Is it in any way encumbered?

Yes, the fact that this is an Eclipse project _seems_ to implicitly answer the question. However Oracle has a history that raises questions. A simple positive statement as to any (or no) restrictions on use would clarify.

Fodder for the README. :)

(Nothing came up in a search. Perhaps I asked the wrong question.)

question

All 10 comments

OpenJ9 is an independent implementation of a Java Virtual Machine built originally by IBM and open sourced under AL2+EPL2 (with secondary license matching OpenJDK's license) in September 2017.

Is that the kind of statement you were looking for? Or are you looking for something even more explicit?

After Oracle bought Sun, one of my (very large) DoD customers reported a
visit from an Oracle representative, who claimed the DoD was several
million licenses out of compliance. The DoD folk were able to face down the
Oracle guy, but this behavior raises questions.

Oracle is at present (still) suing Google, over Java.

As a developer, I am unsure whether basing future projects on the JVM is a
good long-term strategic bet. Oracle's desire to extract revenue might
weigh against.

I recall (somewhat vaguely) that IBM might have some special license
status. Not sure if that is still relevant, or how that reflects on OpenJ9.

Near their end, Sun made some moves to make Java more open. This seemed of
benefit to OpenJDK. Not sure where that lands us, in present.

If I as a developer base a future project on the JVM, am I in jeopardy of
legal blackmail from Oracle, or not?

On Mon, Jun 4, 2018 at 7:03 AM, Mark Stoodley notifications@github.com
wrote:

OpenJ9 is an independent implementation of a Java Virtual Machine built
originally by IBM and open sourced under AL2+EPL2 (with secondary license
matching OpenJDK's license) in September 2017.

Is that the kind of statement you were looking for? Or are you looking for
something even more explicit?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eclipse/openj9/issues/2060#issuecomment-394365915,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANCJ1XDuEL9e27CGsUGQZ7qkoXsj90Xks5t5T4tgaJpZM4UYKAt
.

Hi @pbannister,

The FAQ here may be helpful: http://www.eclipse.org/legal/legalfaq.php

For legal advice, you would have to consult your own attorney to see if these licences are appropriate for your use. For prebuild OpenJDK binaries, including ones with OpenJ9, we recommend going to AdoptOpenJDK.net https://adoptopenjdk.net/?variant=openjdk8-openj9

Incidentally, I submitted a PR (#2064) with additional text for the README, as you suggested an update would be warranted. What do you think of the text I have added?

In case anyone read my comment before I updated the link, I just updated it so that the "FAQ" link actually points at Eclipse's Legal FAQ page rather than the much less "FAQ-ey" EPLv2 license page. Sorry for any confusion.

Curious, that Sun is explicit in the opening page of 1996 JVM specification:

Sun Microsystems, Inc. (SUN) hereby grants to you a fully-paid,

nonexclusive, nontransferable, perpetual, worldwide limited license
(without the right to sublicense) under SUN's intellectual property rights
that are essential to practice this specification. This license allows and
is limited to the creation and distribution of clean room implementations
of this specification that (i) include a complete implementation of the
current version of this specification without subsetting or supersetting,
(ii) implement all the interfaces and functionality of the standard java.*
packages as defined by SUN, without subsetting or supersetting, (iii) do
not add any additional packages, classes or methods to the java.* packages
(iv) pass all test suites relating to the most recent published version of
this specification that are available from SUN six (6) months prior to any
beta release of the clean room implementation or upgrade thereto, (v) do
not derive from SUN source code or binary materials, and (vi) do not
include any SUN binary materials without an appropriate and separate
license from SUN.

Where the more recent JVM specifications seem to entirely omit similar
text. (Or perhaps I just missed?) We are assuming the same status applies
to the current JVM specifications.

In any case, long ago IBM did a clean-room implementation of the JVM, as
allowed in the JVM specification, so IBM is free to choose the license for
their implementation, and IBM has since chosen to open-source their JVM.
This is the basis for OpenJ9.

On Tue, Jun 5, 2018 at 7:06 AM, Mark Stoodley notifications@github.com
wrote:

In case anyone read my comment before I updated the link, I just updated
it so that the "FAQ" link actually points at Eclipse's Legal FAQ page
rather than the much less "FAQ-ey" EPLv2 license page. Sorry for any
confusion.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eclipse/openj9/issues/2060#issuecomment-394722147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANCJyP6reChfFdXKKDIn6H459g170Adks5t5pBfgaJpZM4UYKAt
.

@pbannister Whenever I've looked for it, that approximate text has been in an appendix of the JVM specification.

Thanks. Did not make it down to the end of the document. (Wanted to reply,
but had limited time, earlier.) Seems paragraph 2 of the "Limited License
Grant" says substantially the same, though in less clear language. Also no
mention of "clean-room" implementations.

https://docs.oracle.com/javase/specs/jvms/se10/html/spec-license.html

So...

OpenJ9 is a "clean-room" implementation (originally by IBM) in exact
compliance with the license of the Java Virtual Machine Specification. As
an independent implementation OpenJ9 can be offered under a permissive,
open-source license.

On Tue, Jun 5, 2018 at 7:49 AM, Mark Stoodley notifications@github.com
wrote:

@pbannister https://github.com/pbannister Whenever I've looked for it,
that approximate text has been in an appendix of the JVM specification.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eclipse/openj9/issues/2060#issuecomment-394738546,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANCJ3nedURyLnGO_cQGPjxfNYlGYxVqks5t5pp7gaJpZM4UYKAt
.

@pbannister I'm going to close this issue because I believe your question has been resolved. Please reopen if you don't agree :) .

Note the term "clean room implementation" has been updated to "independent implementation" :) .

Personally, I prefer mentioning "clean room" as that ties back to the
original license for the JVM spec. But I am entirely fine with what you
have done. My main concern was to clarify the legal status of OpenJ9
up-front for new visitors.

Thanks.

On Thu, Jun 7, 2018 at 7:45 AM, Mark Stoodley notifications@github.com
wrote:

@pbannister https://github.com/pbannister I'm going to close this issue
because I believe your question has been resolved. Please reopen if you
don't agree :) .

Note the term "clean room implementation" has been updated to "independent
implementation" :) .

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eclipse/openj9/issues/2060#issuecomment-395447438,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANCJzusCo3hwguYFvIVGGqNIWrDHx_Oks5t6TyjgaJpZM4UYKAt
.

Your attention to detail is laudable :) . Hopefully the use of the currently matching "independent implementation" language + the details in this issue will be sufficient.

Thank you for helping us to clarify this aspect of the OpenJ9 project !

Was this page helpful?
0 / 5 - 0 ratings