Replies: 3 comments
-
Looks like the older maven-assembly-plugin was the culprit. |
Beta Was this translation helpful? Give feedback.
-
not much we can do here as the stacktrace is coming from Apache Maven (assembly plugin). |
Beta Was this translation helpful? Give feedback.
-
Indeed. It's weird that there seems to be some kind of relation between this particular upgrade of Jetty and that old version of the assembly plugin, but it is unlikely worth the effort of digging into that further. Let's leave this discussion for posterity, but I'm happy to leave it at that. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For a reason that's still beyond me, our GitHub workflow that we use for continuous integration consistently fail after upgrading our Jetty dependency from 12.0.21 to 12.0.22.
The build fails on the packaging step, which uses the assembly plugin, as shown in the error below. This shouldn't use Jetty at all, other than perhaps copy the corresponding JAR files into a
lib
directory for our distributable.I have not reproduced this problem locally yet: the build doesn't fail locally (I'm wondering if this is because locally, I have a populated Maven repository, but I've not investigated further yet).
I thought I'd post here, in the off chance that someone recognizes the problem.
Beta Was this translation helpful? Give feedback.
All reactions