All of the artifacts released from the EE4J projects for the
GlassFish 5.1 release were (or should've been) released with the EPL
license.
The conversion from the javax.* Maven GroupId to the jakarta.* Maven
GroupId was not required for that release; some projects made the
change and some did not.
Kevin Sutter wrote on 6/12/19 8:08 AM:
I was
recently reviewing
our content in maven and I came across a javax artifact licensed
under
EPL... It was the 2.1.1 release of JAX-RS...
https://mvnrepository.com/artifact/javax.ws.rs/javax.ws.rs-api/2.1.1
This seems
wrong.
I thought only the jakarta.* namespace in Maven was licensed as
EPL,
not the javax.* namespace. I did a quick review of the javax
artifacts
in maven and this looks to be the only exception. (Of course,
JPA
is also EPL, but that was already developed under the Eclipse
licensing.)
Before I ping
the jax-rs team, I wanted to be sure that I remembered our
processes and
expectations here. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
