Ok, I may be misremembering. (I'm sure there was something
that the PMC said we could change but didn't have to, but I can't
find that detail right now. Module names, maybe? Too many
namespaces all using jakarta.*!!!)
It looks like this JAX-RS 2.1.1 release was done by mistake, or
before the decision to change the GroupId was made. Since there's a
JAX-RS 2.1.2 release with the correct license, is this a big issue?
Are you suggesting that we need to ask for the JAX-RS 2.1.1 release
to be removed from Maven Central because it's using the wrong
GroupId?
Kevin Sutter wrote on 6/12/19 2:23 PM:
Actually, it
was
a requirement to change to the jakarta.* maven groupid. This is
actually
one of the arguments that Dmitry is currently using to put off
the repository
name change that David is proposing.
Since this
jax-rs
2.1.1 release is the only exception that I can find. And, you
don't
seem to be bothered by it, maybe we just leave sleeping dogs
lie... I'm
fine with leaving it, if you are. And, maybe I should equate
"you"
to Oracle and not just you personally, Bill.
Just to
clarify
my question using the Maven repo... Look at this javax groupid
query:
https://mvnrepository.com/search?q=g%3Ajavax
This lists
out
all of the various javax.* groupid packages in Maven. Notice in
the
right hand column where most everything is licensed under
CDDL/GPL. Except
when you get down to line 5 with javax.ws.rs which shows EPL.
(There
are other exceptions to this rule due to Apache licensing and
Eclipse-based
projects. I was just focused on the CDDL vs EPL license.)
Now compare
that
with a jakarta groupid query:
https://mvnrepository.com/search?q=g%3Ajakarta
All of the
"java
ee" APIs that were moved to the Jakarta groupid are properly
identified
with the EPL/EDL license. Even JAX-RS has a proper version with
the
EPL license:
https://mvnrepository.com/artifact/jakarta.ws.rs/jakarta.ws.rs-api/2.1.2
Like I said,
if
nobody seems to think this is an issue, then I'll drop it.
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
From:
Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
Kevin
Sutter <sutter@xxxxxxxxxx>
Cc:
Jakarta
specification committee
<jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
06/12/2019
03:41 PM
Subject:
[EXTERNAL]
Re: [jakarta.ee-spec.committee] javax Maven artifacts using EPL?
The license has nothing to do with
what
GroupId you use, it has to do with the license of the source
code.
And again, the PMC did not require the EE4J projects to
convert
to the jakarta.* Maven GroupIds
Maybe I don't understand what it is you're seeing in the Maven
Central
repository that you think is wrong? The JAX-RS artifact you
pointed
to below does use javax.* and EPL, for reasons I explained.
Maybe
you think we shouldn't have done that, but it was not an
accident.
If you find an artifact licensed with EPL but released from the
old javaee
GitHub organization, or an artifact licensed with CDDL and
released from
an EE4J project, that would be an error.
Kevin Sutter wrote on 6/12/19 1:23
PM:
Bill,
Interesting. I'm not seeing that in the Maven Central
repository.
Only the jakarta.* Maven GroupId seems to be using the EPL
license,
which is what I would have expected. I would not expect javax
GroupId
artifacts to be licensed under EPL.
---------------------------------------------------
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
From: Bill
Shannon <bill.shannon@xxxxxxxxxx>
To: Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>,
Kevin Sutter <sutter@xxxxxxxxxx>
Date: 06/12/2019
02:44 PM
Subject: [EXTERNAL]
Re: [jakarta.ee-spec.committee] javax Maven artifacts using EPL?
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
|
