Thanks Mickael. This is what I thought. Unfortunately, I do not have a local fork of platform set up in our CI so this would be a heavy lift in the short term.
Any thoughts on the ugly approach of replacing the Jetty jars post-build (9.4.31->9.4.34)?
From: <epp-dev-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Reply-To: Eclipse Packaging Project <epp-dev@xxxxxxxxxxx>
Date: Tuesday, November 17, 2020 at 11:48 AM
To: Eclipse Packaging Project <epp-dev@xxxxxxxxxxx>
Subject: Re: [epp-dev] How to update jetty in a fork of epp?
You'll need to locally build a fork of platform to replace the various references to jetty by newer (or more relaxed) ones; then you'll need to re-build the EPP package ensuring your fork is taken into account (it can happen just by `mvn
install`ing Platform then building EPP, which may just consume the locally installed artifacts; or you can use the `-Depp.wormhole.repository=file:/path/to/local/p2/repo/for/platform/build`. It safer if you bump the version by +0.0.1 of the features that do
reference older Jetty; so you can more easily force their inclusion by specifying the version in the .product file.