This repository has been archived by the owner. It is now read-only.

Jersey BOM is broken #3773

Closed
vpavic opened this Issue Feb 19, 2018 · 9 comments

Comments

Projects
None yet
4 participants
@vpavic

vpavic commented Feb 19, 2018

Jersey BOM provides dependency management for org.glassfish.jersey.bundles.repackaged:jersey-jsr166e however for the current 2.26 release this artifact is not available in Maven Central.

@joschi

This comment has been minimized.

joschi commented Mar 6, 2018

Any chance to fix this in a patch release?

@vpavic

This comment has been minimized.

vpavic commented Mar 6, 2018

If the 2.26 release of org.glassfish.jersey.bundles.repackaged:jersey-jsr166e would find its way to Maven Central that would effectively resolve the issue.

@1605200517

This comment has been minimized.

1605200517 commented Mar 6, 2018

@vpavic is this one not what you are looking for (was added after creation of this issue, on 2017-01-31)?
http://repo1.maven.org/maven2/org/glassfish/jersey/bundles/repackaged/jersey-jsr166e/2.26-b02/

@vpavic

This comment has been minimized.

vpavic commented Mar 6, 2018

@1605200517 No, because the BOM in subject is version 2.26.

@1605200517

This comment has been minimized.

1605200517 commented Mar 6, 2018

@vpavic I have to excuse myself for possible misunderstanding of the procedure protocols here, but the sentence above "if the release... would find its way.." sounds somewhat obscure to me.
So, who could do what to help the release finding its way?

@joschi

This comment has been minimized.

joschi commented Mar 6, 2018

@1605200517 The maintainers have to create a release artifact in the correct version and upload it to Maven Central.

@jansupol

This comment has been minimized.

Member

jansupol commented Mar 8, 2018

The change has been done on 2017-02-17, the jsr 166 bits were put to core-common, and the BOM pom was not updated. That's before 2.26-b03 release. We should remove the record from BOM pom.

@vpavic

This comment has been minimized.

vpavic commented Mar 8, 2018

Thanks for the update @jansupol. Do you by any chance have an approximate target date for the next release?

@jansupol

This comment has been minimized.

Member

jansupol commented Mar 26, 2018

The change is submitted, the release is scheduled right after Easter.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.