On 2018-01-23 11:21 AM, Werner Keil
wrote:
So with Vert.x or JNoSQL, should they ever apply EPL2, does
one license have to be "primary" and the other "secondary" or
can they also remain side-by side as they are now with those
projects?
Yes, those projects can move from EPL-1.0+APACHE-2.0 to EPL-2.0+APACHE-2.0
any time that they want.
Except JNoSQL which already uses an EPL 1 based licensing (so
does Yasson and no change is proposed there) if either
MicroProfile components were to migrate under the EE4J TLP or
projects like CDI, Bean Validation, Portlet, etc. all of which
are strictly Apache 2, they will face that question.
If Eclipse MicroProfile ever moved to the EE4J top-level project,
they could retain their existing APACHE-2.0 licensing. There is no
fixed requirement to change licenses, although they can do so if
desired. Eclipse Ozark (MVC) is a current example of that. AFAIK,
Ozark is intending to retain its APACHE-2.0 licensing, which it
can do with agreement of the PMC and the Eclipse Foundation Board.
This is all quite ordinary licensing "stuff" for us.
