Olivier,

It is listed in the parent pom as a module, but I'm guessing it was
excluded from the release because it contained SNAPSHOT dependencies that
were not updated?

I've modified the jetty-bom/pom.xml to use ${project.version} for all it's
dependencies.

I see no reason why we can't try doing a manual release of
just 9.4.6.v20170531 for just this module.... let me try (although it has
been a while since I did a release so it is probably not going to work....
but I'll learn something)

cheers


On 8 June 2017 at 08:27, Olivier Lamy <[email protected]> wrote:

> Hi
> My bad I didn't check the staged release.
> I can help as well.
> Well I don't really understand why it's not deployed as it's part of the
> modules list so mvn release should deploy it.
> are you using some custom script rather than maven release plugin?
>
> On Thu, Jun 8, 2017 at 4:16 PM, Greg Wilkins <[email protected]> wrote:
>
>> Joakim,
>>
>> can't the bom be a module in the build, but without having a parent pom?
>>
>> Let me take responsibility for the bom for a while, as it appears to be
>> causing a lot of heat and I want to work out why.
>>
>> cheers
>>
>>
>> On 7 June 2017 at 22:37, Joakim Erdfelt <[email protected]> wrote:
>>
>>> In the future, pay attention to the announced staged releases, it would
>>> be wise to participate in that testing and not let this slip through again.
>>>
>>> If this can be fixed, it will show up in the next release.
>>> Note: We accept pull requests.
>>>
>>>
>>> Joakim Erdfelt / [email protected]
>>>
>>> On Wed, Jun 7, 2017 at 1:19 PM, Joakim Erdfelt <[email protected]>
>>> wrote:
>>>
>>>> You are correct.
>>>>
>>>> It didn't deploy, as its no longer part of the eclipse jetty maven
>>>> hierarchy.
>>>> Since we do not use the jetty-bom ourselves (and have no earthly idea
>>>> why anyone would want to use it when traditional methods and alternatives
>>>> are much simpler) we did not discover this issue ourselves during the
>>>> announced staged/testing period for this release, and nobody else reported
>>>> this issue to us.
>>>>
>>>> This is the reason it broke -> https://github.com/eclipse/jet
>>>> ty.project/issues/1527
>>>> As it stands currently, the jetty-bom cannot participate in the normal
>>>> release process due that change.
>>>> Its effectively a standalone release ATM. (*really* annoying)
>>>>
>>>>
>>>> Joakim Erdfelt / [email protected]
>>>>
>>>> On Wed, Jun 7, 2017 at 1:28 AM, Filipe Sousa <[email protected]> wrote:
>>>>
>>>>> I can't find the jetty-bom in maven central. The last version is
>>>>> 9.4.5.v20170502
>>>>>
>>>>> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.eclip
>>>>> se.jetty%22%20AND%20a%3A%22jetty-bom%22
>>>>> http://central.maven.org/maven2/org/eclipse/jetty/jetty-bom/
>>>>>
>>>>> > On 6 Jun 2017, at 20:34, Chris Walker <[email protected]> wrote:
>>>>> >
>>>>> > The Jetty team is happy to announce the immediate availability of a
>>>>> new release for the Eclipse Jetty 9.4.x branch.
>>>>> >
>>>>> >
>>>>> >
>>>>> > This release includes several bug fixes and enhancements.
>>>>> Additionally, cookie parsing has been overhauled to maintain compliance
>>>>> with revised specs. It is recommended that users upgrade to the latest
>>>>> version. Patch notes for the release can be found at the end of this 
>>>>> email.
>>>>> >
>>>>> >
>>>>> >
>>>>> > This release available on the Eclipse Jetty project download page or
>>>>> from the Maven Central repository:
>>>>> >
>>>>> >
>>>>> >       • Eclipse: https://www.eclipse.org/jetty/download.html
>>>>> >       • Maven Central: http://central.maven.org/maven
>>>>> 2/org/eclipse/jetty/
>>>>> > Documentation for this release can be found on the Eclipse Jetty
>>>>> project site:
>>>>> >
>>>>> >
>>>>> >       • https://www.eclipse.org/jetty/documentation/
>>>>> > If you find any issues with this release, or if you want to suggest
>>>>> future enhancements, please file an issue on the Jetty GitHub page:
>>>>> >
>>>>> >
>>>>> >       • https://github.com/eclipse/jetty.project/issues/new
>>>>> > Commercial production and development support for Jetty is offered
>>>>> through Webtide (www.webtide.com). Please contact us for more
>>>>> information or email [email protected] to learn more.
>>>>> >
>>>>> >
>>>>> > Change logs for these releases are listed below.
>>>>> >
>>>>> >
>>>>> >
>>>>> > Best Regards,
>>>>> >
>>>>> > The Jetty Development Team
>>>>> >
>>>>> >
>>>>> >
>>>>> > jetty-9.4.6.v20170531 - 31 May 2017
>>>>> >  + 523 TLS close behaviour breaking session resumption
>>>>> >  + 1108 Please improve logging in SslContextFactory when there are
>>>>> no approved cipher suites
>>>>> >  + 1505 Adding jetty.base.uri and jetty.home.uri
>>>>> >  + 1514 websocket dump badly formatted
>>>>> >  + 1516 Delay starting of WebSocketClient until an attempt to
>>>>> connect is made
>>>>> >  + 1520 PropertyUserStore should extract packed config file
>>>>> >  + 1526 MongoSessionDataStore old session scavenging is broken due
>>>>> to the missing $ sign in "and" operation
>>>>> >  + 1527 Jetty BOM should not depend on jetty-parent
>>>>> >  + 1528 Internal HttpClient usages should have common configurable
>>>>> technique
>>>>> >  + 1536 Jetty BOM should include more artifacts
>>>>> >  + 1538 NPE in Response.putHeaders
>>>>> >  + 1539 JarFileResource mishandles paths with spaces
>>>>> >  + 1544 Disabling JSR-356 doesn't indicate context it was disabled
>>>>> for
>>>>> >  + 1546 Improve handling of quotes in cookies
>>>>> >  + 1553 X509.isCertSign() can throw ArrayIndexOutOfBoundsException
>>>>> on non-standard implementations
>>>>> >  + 1556 A timing channel in Password.java
>>>>> >  + 1558 When creating WebAppContext without session-config and with
>>>>> NO_SESSIONS throws NPE
>>>>> >  + 1567 XmlConfiguration will start the same object multiple times
>>>>> >  + 1568 ServletUpgradeRequest mangles query strings containing
>>>>> percent-escapes by re-escaping them
>>>>> >  + 1569 Allow setting of maxBinaryMessageSize to 0 in WebSocketPolicy
>>>>> >  + 1579 NPE in Quoted Quality CSV
>>>>> > _______________________________________________
>>>>> > jetty-users mailing list
>>>>> > [email protected]
>>>>> > To change your delivery options, retrieve your password, or
>>>>> unsubscribe from this list, visit
>>>>> > https://dev.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://dev.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://dev.eclipse.org/mailman/listinfo/jetty-users
>>>
>>
>>
>>
>> --
>> Greg Wilkins <[email protected]> CTO http://webtide.com
>>
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>
>
>
> --
> Olivier
>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>



-- 
Greg Wilkins <[email protected]> CTO http://webtide.com
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to