That's the BSD license, which is listed here: (and indicates the source/binary under that license can be included in Apache products).

Despite being a common license, it's always a little hard for someone new to Open Source licensing to recognize as it often doesn't say 'BSD'. See this link for the format of the license: As you can see, you replace bits when you use it, thus all the uses of the BSD licenses look a little bit different.


On Tue, Jan 27, 2015 at 3:58 AM, Chia-Hung Lin <> wrote:
Thanks for the information. It's very clear.

The last question. Scala's licensed under [1], so assuming it's legal
to use it's nsc (compiler package) code because its license is not
listed in [2] and does not violate Apache's. Am I correct in that

Thanks again for kindly help!


On 27 January 2015 at 18:43, Mark Thomas <> wrote:
> On 26/01/2015 09:45, Chia-Hung Lin wrote:
>> Hi,
>> I have a naive question regarding to include the methods like
>> Main.compile in com.sun package in the project source code.
>> For instance, in our project like hama if there is a source file that
>> makes use of to runtime compile java sources
>> into classes. Is it legal to release or include that source with
>> project?
> Legally, yes that is fine. You can reference internal JVM vendor classes
> if you wish.
> What you may not do is include tools.jar in your distribution since the
> license for that JAR is not compatible with distribution under the ALv2.
> Mark
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail: