Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mpc-dev] remediation testing in mpc

On 04.06.2013 23:21, Oberhuber, Martin wrote:
> I'm surprised that so many solutions fail without remediation - especially when you install on top of the Standard package.
> Perhaps I'm misunderstanding the purpose of remediation, but I thought that it was good for resolving conflicting dependencies by allowing to upgrade what I have installed. So when you install Maven for WTP on Kepler Standard, I cannot quite see what conflicts would be resolved ?
> Similar for Github for Mylyn, or especially P4Eclipse ? These should be "plain add-ons" so I can't quite see why they would have to upgrade my base ?
> Does anybody have an explanation for this ?

Yes. The most frequent reason is dependencies with an upper version bound
that is lower than what is in Kepler.

Back to the top