We would like to Zulu Community JRE with our product as bundle. Is there any license problem?
Thanks for help
This sort of question often comes up in the context of including OpenJDK (or Zulu) in otherwise non-open source software products.
For starters, I would refer you to the OpenJDK FAQ for Oracle’s current answers regarding licensing and legal questions. See http://openjdk.java.net/faq/ . E.g. as noted there, “…OpenJDK is released under an well-known open-source licensing model, that places no restrictions on your ability to run OpenJDK.” Running and redistribution have potentially different implications. Since no specific legal advice or answers are provided with OpenJDK or the FAQ in relation to redistributing OpenJDK and/or bundling within other products, you (or your legal advisor) would probably need to read through the various licenses and analyze their specific relationship to each other and to your own product license to make your own determination.
Our Zulu Embedded product is meant for exactly these sorts of embedding/bundling OEM situations. We provide our customers with specific certification of license implications when bundling certified Zulu Embedded builds in products. This certification is based on detailed analysis of the actual sources used to build each specific JDK or JRE package.
Hopefully this helps. In summary from a licensing perspective, the Community edition is “as is”.
Sorry to bring up an old topic. Just wondering if there are any updates on this as we are looking to redistribute the community edition of Zulu within an application that runs on Windows.
The OpenJDK allows you to distribute java with your commercial software provided you are not actually changing the JVM itself (and meeting the other terms (http://openjdk.java.net/legal/gplv2+ce.html). This is the point of GPLV2 with Classpath exception.
The issue is that there is no Windows version of the OpenJDK. Are Azul also saying this? The download suggests this by providing a license of GPLV2 with CE. All 3rd party libraries used are I presume all even less restrictive e.g. apache, mit etc.
Thanks for the help.
If I put on my Azul Sales & Marketing hat, I would say to you its worth looking into Zulu Embedded for your application. By considering a subscription, where cost can be managed to keep it from being prohibitory, you would get Azul support throughout both the technical and licensing/legal guidance for redistributing Zulu binaries today, plus on-going help moving forward throughout future Java and OpenJDK release cycles.
Putting on my Community leader hat, I would need to admit to you that I know for a fact many people today are shipping Zulu community binaries within their products without working with Azul at all. Either they are fluent in the practical use of GPL+ CE licensed components inside commercial products, or they are taking a risk, whether calculated or not.
I cannot give you business or legal advice in this public forum. But I can recommend that if you are on the fence at all, please contact Azul to learn all your options and weigh them.
My scenario is like following…
1)I have downloaded Zulu on my system and developed a GUI app to work with Postgresql backend db. (All are on same Desktop/laptop machine)
2) I want to sell this to my customers but i have developed this as reference, in practice i will go to customer understand their custom requirement and build similar like software on their machine (so its like service).
3)I would ask them to download the Zulu jdk and install it on their machine as a prerequisite and on top of that i would build and create app as per customer requirement.
Do i still need to contact Zulu and pay any fee for this ? I am individual developer (freelancer) and it would be hard to pay large licensing costs.
Hi Sam. There are no field of use restrictions for public Zulu downloads. That’s part of the GPL license under which Zulu is offered at its foundation. Your customers can download and use Zulu for any purpose. Should your customers require Java support and updates, then you should talk to Azul about the Zulu Enterprise product. Should you wish to provide your code under a closed source license, then you should talk to Azul about the Zulu Embedded product.
We totally understand that indie developers often feel left out when licensing and fee schedules are designed for corporate B2B users. I’ll be brutally honest and say that Azul is a for-profit company with a direct sales force targeting B2B accounts. But we do hope that indie and smaller ISVs still consider Zulu as reliable platform for their Java applications, too. Azul just cannot take on cost of creating tailored solutions for community requests, which is why I described community editions remaining “as is” in my earlier response in this thread. Community downloads by design are full JDKs suitable for development and debugging. The Enterprise and Embedded products also offer JREs, Compact Profiles, and other packaging alternatives made to fit customer production operations requirements.
Hopefully this helps your decision.