New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build because of missing Jetty dependency #110
Comments
It seems that the Jetty P2 repo has been aggressively cleaned-up when they released a new version. The current one is: https://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.4.44.v20210927/ The repository doesn't seem to contain composite metadata, so we can't use a more stable repository such as |
- Update the jetty P2 repo URL in the target platform fixes #110
Thanks for the explanation and the fix. It seems related to jetty/jetty.project#6403. Jetty maintainers introduced the new feature to distribute p2 update site as standard Maven artifacts. |
Most Eclipse P2 repos list their contents, so if you go one or two level ups from a P2 repo URL, you can see related files (including repositories). So I simply checked
Indeed, we should consider updating Jetty and use the Maven P2 repos. I'll check with the other EMF.Cloud projects to see if this can be done. |
OK I'm pretty sure that I checked https://download.eclipse.org/jetty/updates/jetty-bundles-9.x/ and that it was empty. Anyway the fact that this update site is not "stable" will cause the same issue in some weeks/months. Closing but interested in future issues to keep track of changes in this repository and in eclipse-emfcloud / eclipse-glsp about this topic. IMHO some other dependencies in "unstable" should be using this new paradigm of p2 update site as standard Maven artifacts (when available). |
110: Unable to build because of missing Jetty dependency
When running
./build.sh
the Maven build fails because of this:@ndoschek : I noticed you already had such an issue in eclipse-emfcloud/emfcloud-modelserver#125
It seems that Jetty is no longer provided as a p2 update site, isn't it ?
The text was updated successfully, but these errors were encountered: