-
Notifications
You must be signed in to change notification settings - Fork 17
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
Linuxtools docker resolution problem #232
Comments
At the moment there are some resolution issues on the nightly versions of LinuxTools docker components, so for now use the latest release rather than nightly. See eclipse-linuxtools/org.eclipse.linuxtools#232
There is nothing more I plan for this cycle. Maybe in the future I'll try to move docker-client to smth newer than 5.x but I'm tired of this effort now and the main driver is moving to Maven wherever possible. |
Ok I'll dig in a little more because Linux tools docker nightly isn't resolving at the moment and there are multiple versions of guava in the repo. |
This comes from the update in e1c13df for guava 32.1.1 + dependency on lsp4e -> wikitext -> guava 31.1.0 |
I don't know why it has started failing for CDT - but AFAICT it looks like com.google.guava.failureaccess is not provided anywhere in the CDT target platform (anymore?) The https://download.eclipse.org/linuxtools/updates-docker-nightly/ is in an odd state now - it republishes a seemingly random set of its dependencies, including eclipse projects like LSP4E and guava, but not dependencies of LSP4E like wikitext and tm4e. However this does not seem to be a recent change so I am going to simply add more stuff to cdt.target to get it to work with the recent updates you (@akurtakov) did. |
At the moment there are some resolution issues on the nightly versions of LinuxTools docker components, so for now use the latest release rather than nightly. See eclipse-linuxtools/org.eclipse.linuxtools#232
The commit resolves the resolution error that was raised in eclipse-linuxtools/org.eclipse.linuxtools#232 If I can reproduce this error more standalone I will raise it with PDE as having to include failureaccess from a p2 site sounds like a bug. Look in the PR associated with this commit for a link to the PDE bug (if I raise one)
I have raised eclipse-pde/eclipse.pde#675 as it looks like there is a resolution error that the recent changes in linuxtools exposes. |
The commit resolves the resolution error that was raised in eclipse-linuxtools/org.eclipse.linuxtools#232 I have raised an issue in PDE here: eclipse-pde/eclipse.pde#675
The commit resolves the resolution error that was raised in eclipse-linuxtools/org.eclipse.linuxtools#232 I have raised an issue in PDE here: eclipse-pde/eclipse.pde#675
At the moment there are some resolution issues on the nightly versions of LinuxTools docker components, so for now use the latest release rather than nightly. See eclipse-linuxtools/org.eclipse.linuxtools#232
The commit resolves the resolution error that was raised in eclipse-linuxtools/org.eclipse.linuxtools#232 I have raised an issue in PDE here: eclipse-pde/eclipse.pde#675
@akurtakov I know you are working on this at the moment, but in recent days the Eclipse CDT build breaks:
See PRs:
If you aren't done yet I will revert to latest release of linuxtools docker for now and rejoin nightly when you want me to test it out again.
The text was updated successfully, but these errors were encountered: