Re: [jersey-dev] [External] : Releasing Jersey 4.0.1

[Jan Supol <jan.supol@xxxxxxxxxx>]

Hi,

Jersey-Constants is a new module with some HTTP related constants. Probably, the module does not contain FELIX plugin to have OSGi headers, but since it is not used in GF, it should not be a blocker for the release.

I was under an impression that Maxim was fixing it (https://github.com/eclipse-ee4j/jersey/pull/6039), but it is not merged to 4.0, yet.

The other reported issue says the javadoc jar of jersey-container-helidon-http is not released.

Thanks,

Jan

Confidential- Oracle Internal

---

From: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Sent: Friday, January 30, 2026 1:47 PM
To: Jan Supol <jan.supol@xxxxxxxxxx>
Cc: jersey-dev@xxxxxxxxxxx <jersey-dev@xxxxxxxxxxx>; David Matějček <dmatej79@xxxxxxxxx>
Subject: Re: [External] : [jersey-dev] Releasing Jersey 4.0.1

 

Hi,

That's a very interesting test, thanks!

There are two tests already failing (I noticed they failed for the 4.0.0 release too):

[ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.070 s <<< FAILURE! -- in org.glassfish.jersey.test.artifacts.DownloadBomPomDependencies
[ERROR] org.glassfish.jersey.test.artifacts.DownloadBomPomDependencies.testDownloadBomPomDependencies -- Time elapsed: 0.390 s <<< ERROR!
org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.glassfish.jersey.containers:jersey-container-helidon-http:jar:javadoc:4.0.2 in sonatype-nexus-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:425)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:229)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:207)
at org.eclipse.aether.internal.impl.Defaul

and

(pass) 'Multi-Release: true' set for jersey-common-4.0.2.jar
(FAIL) jersey-constants-4.0.2.jar DOES NOT CONTAIN Bundle-Name attribute
(FAIL) jersey-constants-4.0.2.jar DOES NOT CONTAIN Bundle-Version attribute
(FAIL) No Import-Package in module jersey-constants-4.0.2.jar
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.120 s <<< FAILURE! -- in org.glassfish.jersey.test.artifacts.ManifestTest
[ERROR] org.glassfish.jersey.test.artifacts.ManifestTest.testHasOsgiManifest -- Time elapsed: 0.078 s <<< FAILURE!
java.lang.AssertionError: Some error occurred, see previous messages
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.glassfish.jersey.test.artifacts.ManifestTest.testHasOsgiManifest(ManifestTest.java:93)

But otherwise this looks kinda amazing. Thanks again!

Kind regards,

Arjan Tijms

On Fri, 23 Jan 2026 at 16:13, Jan Supol <jan.supol@xxxxxxxxxx> wrote:

Hi Arjan,

We have developed some tests to run on the maven artifacts that checks the release jars contain all the formalities. I.e. Licenses, multirelease, jdk version, documentation jars, etc.

The tests are located in tests/release-test, to be executed with the version of the release. For instance -Djersey.version=4.0.1.

Without the version, only a subset of tests is executed.

The same is with Tyrus.

HTH,

Jan

Confidential- Oracle Internal

---

From: jersey-dev <jersey-dev-bounces@xxxxxxxxxxx> on behalf of Arjan Tijms via jersey-dev <jersey-dev@xxxxxxxxxxx>
Sent: Thursday, January 22, 2026 7:57 AM
To: jersey-dev@xxxxxxxxxxx <jersey-dev@xxxxxxxxxxx>
Cc: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>; David Matějček <dmatej79@xxxxxxxxx>
Subject: [External] : [jersey-dev] Releasing Jersey 4.0.1

 

Hi,

I've released Jersey 4.0.1-M1. It's a milestone, since some things have changed regarding publishing to Maven Central, and I wanted to be sure we publish the right thing.

If there are no objections or concerns, I would like to release 4.0.1 soon.

Thoughts?

Kind regards,

Arjan Tijms