Here's the discussion:
https://groups.google.com/d/topic/h2-database/lqKsP8xnzyQ/discussion
At that time, Thomas suggested invoking the "auto-upgrade" clause of MPL 1.1 that allows a redistributor of MPL 1.1 code to upgrade it to MPL 2.0. However, it turns out upgrading the license that way does not make the license GPL-compatible, because then Exhibit B of MPL 2.0 is invoked, which declares that the work is "Incompatible with Secondary Licenses". (See below.)
We would like to distribute H2 with a bunch of GPL code. Thomas, would you be willing to again consider updating the license to MPL 2.0?
Thanks very much,
Dan
---
For details about why the redistribution upgrade doesn't create GPL compatibility, see these links (I include the most relevant quotes from each):
http://www.gnu.org/licenses/license-list.html#MPL-2.0
"...Software under previous versions of the MPL can be upgraded to version 2.0, but any software that isn't already available under one of the listed GNU licenses must be marked as Incompatible With Secondary Licenses. This means that software that's only available under previous versions of the MPL is still incompatible with the GPL and AGPL."
https://www.mozilla.org/MPL/2.0/Revision-FAQ.html#upgrading-someone-elses-code
"...If you received the code under only MPL 1.1, and not a combination of the MPL plus a member of the GNU family of licenses (such as the Mozilla Tri-License), then you must also add the text of Exhibit B to the license header."
--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h2-database...@googlegroups.com.
To post to this group, send email to h2-da...@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.