|Re: [cross-project-issues-dev] weird MPC versions causing grief|
> When you say "The update mechanism of MPC adds the update site of the > newest compatible version" I wonder how exactly that happens? I ask > because what you describe below is exactly what would happen if the > content metadata for http://download.eclipse.org/mpc/releases/1.7.7 is > loaded and used during resolution, but the corresponding artifact metadata > is not loaded and not used during the installation phase. I know that p2 > records these things (repositories) as two separate preferences even though > you don't see it that way in the UI; you have to dig deep to find that > information... Yes, this is exactly what is happening. See my other reply. I'll have a fix in a moment - just wondering now if we should retroactively try to fix the old breakage as well and add missing artifact repos to the list.
Back to the top