OK, so I think I lucked out, both the oss.sonatype.org and git gods were smiling on me tonight. In this situation the jetty-bom-9.4.13.v20181111.pom was present on the staging repository, but the xml was bad and referenced 9.4.13-SNAPSHOT (ugh. just like the git tag link shows). It seems that the oss.sonatype.org release process filtered it out and didn't attempt to cache it locally. Which helped greatly this time. The last time this happened, oss.sonatype.org and maven central disagreed on what the state of that particular pom artifact was. It went smoother then I expected for the process this time. (no tag tho, not sure it's need for this minor bump <https://github.com/eclipse/jetty.project/commit/22484a18ce3ff7d04e0248e498cfc36487bb24ac> )
Keep an eye out on maven central for it. Joakim Erdfelt / [email protected] On Mon, Nov 12, 2018 at 6:45 PM Joakim Erdfelt <[email protected]> wrote: > You are absolutely right, the jetty-bom is missing. :-( > > This is because the jetty-bom is a bastard module that is impossible to > play nice within the maven, all plugins refuse to updates the versions > within it, as it's not quite within the reactor, nor capable of > participating within the normal build hierarchy due to the inane rules on > boms that force this behavior on the rest of the project. > > https://github.com/eclipse/jetty.project/blob/jetty-9.4.13.v20181111/jetty-bom/pom.xml#L5 > > Unfortunately, now that the tag jetty-9.4.13.v20181111 has been created we > cannot touch that tag (as they are referenced within the jar artifacts > themselves via both the ref and the commit ids). > We cannot release jetty-bom using the normal build tools and processes now. > This will be a manual process, be aware that it can take a while to sort > out (up to a week). > > Joakim Erdfelt / [email protected] > > On Mon, Nov 12, 2018 at 5:19 PM Steven Schlansker < > [email protected]> wrote: > >> Hi Joakim, >> >> Excited to try Jetty 9.4.13! However, it seems that the `bom` artifact >> may have been left behind. >> >> According to Maven Central, >> >> org.eclipse.jetty >> Artifact ID >> jetty-server >> Latest Version >> 9.4.13.v20181111 >> >> org.eclipse.jetty >> Artifact ID >> jetty-bom >> Latest Version >> 9.4.12.v20180830 >> >> I apologize if this is due to impatience coupled with inconsistent >> mirroring delays or some other technical glitch, but it sure looks like the >> `jetty-bom` artifact may not have been released. >> >> > On Nov 12, 2018, at 11:23 AM, Joakim Erdfelt <[email protected]> >> wrote: >> > >> > The Jetty team is happy to announce the immediate availability of a >> newest release for the Eclipse Jetty 9.4.x branch. >> > ... >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/jetty-users >> >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
