[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] Unsatisfied dependency when updating to EGit 2.0.0.x from nighly-build repo
|
Thanks for confirming the direction. I now left a comment on the last pull request [1] for the equivalent issue during EGit switching release version from 1.2.0 to 1.3.0. I did not figure out, how to create an own pull request on github.
[1]
https://github.com/sonatype/m2eclipse-egit/pull/1 On Fri, Apr 13, 2012 at 9:39 AM, Alex Blewitt
<alex.blewitt@xxxxxxxxx> wrote:
It looks like the Maven SCM handler needs to be updated. Basically it's saying that EGit 1.3.0 needs to have org.eclipse.egit.core 2.0, but the Maven handler needs org.eclipse.egit.core between 1.0 and 2.0(exclusive).
The core bundle is marked as a singleton, possibly because it uses the Equinox extension registry, and so it can't install both at once.
You may find that if you uninstall the Maven component, upgrade EGit, and then install a later version of Maven (e.g. 0.15) the version requirements may be fixed.
Alternatively if you add an update site in for Maven containing the new component then you may be able to upgrade all in one go. But the Maven components are scattered through time and space and it's not always obvious which sites you need in order to upgrade all the components.
Alex
On 13 Apr 2012, at 07:39, Andreas Weise wrote:
> Hi Egit-lers,
>
> somehow I am not able to install the 2.0.0.x version.
>
> Am I right, the root cause is the unsatisfied dep:
> From: Maven SCM Handler for EGit 0.14.0.201110251725 (org.sonatype.m2e.egit 0.14.0.201110251725)
> To: bundle org.eclipse.egit.core [1.0.0,2.0.0)
>
> So its more or less an issue of the version range of org.sonatype.m2e.egit from sonatype? And will only occur in case Maven SCM Handler for EGit is preinstalled?
>
> Let me know your thoughts.
>
> Thanks
> Andreas
>
>
>
> Below you get the full trace:
>
> Your original request has been modified.
> "Eclipse EGit" is already installed, so an update will be performed instead.
> "EGit Mylyn" is already installed, so an update will be performed instead.
> "Eclipse JGit" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Eclipse EGit 2.0.0.201204120545 (org.eclipse.egit.feature.group 2.0.0.201204120545)
> Software currently installed: agito Eclipse IDE 0.0.2.201204122054 (agito-eclipse-ide 0.0.2.201204122054)
> Only one of the following can be installed at once:
> Git Team Provider Core 2.0.0.201204120545 (org.eclipse.egit.core 2.0.0.201204120545)
> Git Team Provider Core 1.3.0.201202151440-r (org.eclipse.egit.core 1.3.0.201202151440-r)
> Cannot satisfy dependency:
> From: agito Eclipse IDE 0.0.2.201204122054 (agito-eclipse-ide 0.0.2.201204122054)
> To: de.agito.infra.ide.product_feature.feature.group [0.0.2.201204122054]
> Cannot satisfy dependency:
> From: agito IDE branding 0.0.2.201204122054 (de.agito.infra.ide.product_feature.feature.group 0.0.2.201204122054)
> To: org.sonatype.m2e.egit.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Eclipse EGit 2.0.0.201204120545 (org.eclipse.egit.feature.group 2.0.0.201204120545)
> To: org.eclipse.egit.core [2.0.0.201204120545]
> Cannot satisfy dependency:
> From: Maven SCM Handler for EGit 0.14.0.201110251725 (org.sonatype.m2e.egit 0.14.0.201110251725)
> To: bundle org.eclipse.egit.core [1.0.0,2.0.0)
> Cannot satisfy dependency:
> From: Maven SCM Handler for EGit 0.14.0.201110251725 (org.sonatype.m2e.egit.feature.feature.group 0.14.0.201110251725)
> To: org.sonatype.m2e.egit [0.14.0.201110251725]
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/egit-dev
