[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jersey-dev] 2.28 release?
|
Hi,
The transition of Java EE to Jakarta EE should be verified before any
Jakarta EE project is released to maven central. The verification
include for instance the following steps:
- check the project is still functional (passes internal tests)
- the compatibility with Java EE 8 is checked - Java EE TCK passes with
the Jakarta EE projects integrated to Eclipse Glassfish
- the distributed bits include requested legal material
The verification of Jakarta EE is still in progress. As a single detail
that needs to be adjusted in one project can affect the other projects,
rather than making multiple releases of each project that would cause
making multiple releases of other project when updating dependency, most
projects chose to be released at once after the verification is over.
That should have been done during January. Then Jersey 2.28 is going to
be released, along with most other projects. So far, Jersey is only in
staging repository and is used internally for the verification.
The automated staging jobs unfortunately create (temporary) version tags
and branches in GitHub repository, which could confuse you.
Thank you,
Jan
On 04.01.2019 7:45, Markus KARG wrote:
Jan's blog says he plans to release this month.
-Markus
*From:*jersey-dev-bounces@xxxxxxxxxxx
[mailto:jersey-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Christian Kaltepoth
*Sent:* Freitag, 4. Januar 2019 07:22
*To:* jersey developer discussions
*Subject:* Re: [jersey-dev] 2.28 release?
AFAIK the release review
<https://projects.eclipse.org/projects/ee4j.jersey/reviews/2.28-release-review>
for 2.28 is still pending. The artifacts are currently just available
in the staging repository.
Am Fr., 4. Jan. 2019 um 05:25 Uhr schrieb Scott Lewis
<slewis@xxxxxxxxxxxxx <mailto:slewis@xxxxxxxxxxxxx>>:
Hi,
It looks from the Jersey project page [1] that the 2.28 release
has been
completed on 11/22/2018, but I can't seem to find the p2 repo for
2.28. Could you please point me to that?
BTW, as project lead for ECF, I've created a Jax-RS distribution
provider for ECF's impl of OSGi R7 remote services [2], and this
distribution provider can use either Jersey or CXF to provide remote
services. It's currently using 2.22.x of Jersey, however, and I
would
like to move to latest (e.g. 2.28) when I get a hold of it.
Thanksinadvance,
Scott
[1] https://projects.eclipse.org/projects/ee4j.jersey
[2] https://github.com/ECF/JaxRSProviders
_______________________________________________
jersey-dev mailing list
jersey-dev@xxxxxxxxxxx <mailto:jersey-dev@xxxxxxxxxxx>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jersey-dev
--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal
_______________________________________________
jersey-dev mailing list
jersey-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jersey-dev