Eclipse Community Forums: AMP » Conflicting dependency when installing Ascape Documentation and Source

Home » Archived » AMP » Conflicting dependency when installing Ascape Documentation and Source

Conflicting dependency when installing Ascape Documentation and Source [message #632712]

Wed, 13 October 2010 23:28

Eclipse User

Cannot complete the install because of a conflicting dependency.
  Software being installed: Ascape Documentation and Source 5.6.0.201008061507-0--cKzH3E (org.ascape.doc.feature.group 5.6.0.201008061507-0--cKzH3E)
  Software currently installed: AMP All-In-One SDK (Incubation) 0.8.0.v201007010013-18N-8YZHJ06n65WIwg4Ss5fqXtlF (org.eclipse.amp.all.feature.group 0.8.0.v201007010013-18N-8YZHJ06n65WIwg4Ss5fqXtlF)
  Only one of the following can be installed at once: 
    Ascape Core Source 5.6.0.201008061507 (org.ascape.core.source 5.6.0.201008061507)
    Ascape Core Source 5.2.0 (org.ascape.core.source 5.2.0)
  Cannot satisfy dependency:
    From: Source for Ascape Core Framework 5.6.0.201008061507 (org.ascape.core.source.feature.group 5.6.0.201008061507)
    To: org.ascape.core.source [5.6.0.201008061507]
  Cannot satisfy dependency:
    From: Ascape Documentation and Source 5.6.0.201008061507-0--cKzH3E (org.ascape.doc.feature.group 5.6.0.201008061507-0--cKzH3E)
    To: org.ascape.core.source.feature.group 0.0.0
  Cannot satisfy dependency:
    From: AMP All-In-One SDK (Incubation) 0.8.0.v201007010013-18N-8YZHJ06n65WIwg4Ss5fqXtlF (org.eclipse.amp.all.feature.group 0.8.0.v201007010013-18N-8YZHJ06n65WIwg4Ss5fqXtlF)
    To: org.eclipse.amp.source.feature.group [0.8.0.v201007010013-18V-FAFkNZNOfNZNNZw9bTtFsqSM]
  Cannot satisfy dependency:
    From: org.eclipse.amp.escape.source.feature.group 0.8.0.v201007010013-67u-BmaZGTz-vHPHHgWA77AG
    To: org.ascape.core.source [5.2.0]
  Cannot satisfy dependency:
    From: AMP Source (Incubation) 0.8.0.v201007010013-18V-FAFkNZNOfNZNNZw9bTtFsqSM (org.eclipse.amp.source.feature.group 0.8.0.v201007010013-18V-FAFkNZNOfNZNNZw9bTtFsqSM)
    To: org.eclipse.amp.escape.source.feature.group [0.8.0.v201007010013-67u-BmaZGTz-vHPHHgWA77AG]

Because org.eclipse.amp.escape.source has org.ascape.core.source v5.2

How can I get org.ascape.core.source v5.6 source installed?

Re: Conflicting dependency when installing Ascape Documentation and Source [message #632717 is a reply to message #632712]

Thu, 14 October 2010 00:16

Eclipse User

Oliver Mannion wrote on Wed, 13 October 2010 23:28

[code]Cannot complete the install because of a conflicting dependency.
Because org.eclipse.amp.escape.source has org.ascape.core.source v5.2

How can I get org.ascape.core.source v5.6 source installed?

Hi Oliver,

I'm sorry you're having issues with this.. This is something that has been troublesome all along. I assume that you're able to install everything else, just not the docs and source?

As background, the basic problem is that we end up with two different versions of the ascape core -- one comes from the Ascape site and the other form the Eclipse site! We can't keep the dependency in one place. If we built Ascape core just on Ascape/Sourceforge, we'd need to introduce an externally maintained dependency for the Eclipse build == big no no WRT Eclipse IP. And if we built on Eclipse only, then anytime we wanted to deliver a change for Ascape, we'd need to put it through Eclipse IP process. Its giving me a headache just describing the issue.

Now, for further fun, Eclipse detests having two different versions of the same plugin installed at the same time. So make them the same version you say. Well yes, that would be good, but see above, we only want to do this when it is really warranted as we have to put it through Eclipse IP process. But worse, two plugins with the same version number but different actual build IDs/times can cause things to fail in really novel and non-transparant ways.

What does that mean? We need to prevent people from installing core from both places. And there are pieces there that could work better, because under certain circumstance, which I admit to not having pinned down, you can't install both at the same time. But, even if this weren't an issue at all, it still would be for docs, because that includes both the Swing and (you got it) the Ascape core source, and source follows the same rules -- you can't have both. So what I think I'm going to actually have to do is separate out the core docs from the docs feature and provide that separately. And then I think I'm probably going to have to set up a feature like "Ascape for AMP users".

exhaustedly,

Miles

Re: Conflicting dependency when installing Ascape Documentation and Source [message #632719 is a reply to message #632717]

Thu, 14 October 2010 00:32

Eclipse User

Sounds frustrating although it's not too bad for me, I can always do a manual install of the source Smile

The curious thing is I am able to install org.ascape.core_5.6.0 from the http://ascape.sourceforge.net/eclipse update site without a conflicting dependency error, I just can't install org.ascape.core.source 5.6.0. If I can get the binaries I thought I would have been able to get the source or there might have been a way to make the source dependency compatible like the binaries.

Thanks Miles!

Re: Conflicting dependency when installing Ascape Documentation and Source [message #632747 is a reply to message #632717]

Thu, 14 October 2010 03:11

Eclipse User

Sounds frustrating although it's not too bad for me, I can always do a manual install of the source Smile

Re: Conflicting dependency when installing Ascape Documentation and Source [message #632975 is a reply to message #632747]

Thu, 14 October 2010 16:55

Eclipse User

Oliver Mannion wrote on Thu, 14 October 2010 03:11

Sounds frustrating although it's not too bad for me, I can always do a manual install of the source Smile

Oliver, can you confirm that you have the binaries for both 5.6.0 and 5.2.0 in your installation? If so, what order did you do the install in? Because you're right, if we can get that working well then the two versions of source shouldn't be an issue either.

Re: Conflicting dependency when installing Ascape Documentation and Source [message #632985 is a reply to message #632975]

Thu, 14 October 2010 17:49

Eclipse User

I have the binaries for 5.6 but not 5.2. This come about by installing AMP as per the published instructions and then installing Ascape Core Framework via the http://ascape.sourceforge.net/eclipse update site

Re: Conflicting dependency when installing Ascape Documentation and Source [message #632988 is a reply to message #632985]

Thu, 14 October 2010 18:01

Eclipse User

Oliver Mannion wrote on Thu, 14 October 2010 17:49

Yes that makes sense. I think the rule is that you are allowed to upgrade as long as you don't violate the version constraints on the original for already installed features -- which we don't because the dependency allows higher versions. But if you install Ascape first you'll have trouble because ..hmm... you shouldn't have trouble there but I think that somehow having p2 (Eclipse provisioning) expecting that it should get 5.2.0 from the same repos may screw things up. Anyway, the source builds have all changed because we're using Buckminster now for builds (or trying to anyway) and perhaps that is out of synch now. I won't know until I can get the Eclipse hosted build working. (&*(^#)

Re: Conflicting dependency when installing Ascape Documentation and Source [message #633238 is a reply to message #632747]

Fri, 15 October 2010 15:27

Eclipse User

Oliver Mannion wrote on Thu, 14 October 2010 03:11

If I can get the binaries I thought I would have been able to get the source or there might have been a way to make the source dependency compatible like the binaries.

Thanks Miles!

NP.

And, yes, one would think so.. But the source is built in an entirely different way from the binaries -- they're actually created automatically -- and the dependencies are completely different as well. I think we need to separate out the source bundles but that's not ideal either because it requires people to select two different sets of source separately.

BTW, I'm going to move things over to Git, hopefully that will make non-Eclipse builds easier as we might be able to do something clever by reapplying a change to version dependencies to the Eclipse features when we build externally.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=327944

Even more relevant to you, I'm thinking we should move Ascape while we're at it. That will make it easier to integrate with your other tools as well, since you'll be able to patch changes back in, etc...

Re: Conflicting dependency when installing Ascape Documentation and Source [message #633433 is a reply to message #633238]

Sun, 17 October 2010 16:27

Eclipse User

Oki doki, I'll brush up on Git!

Re: Conflicting dependency when installing Ascape Documentation and Source [message #636565 is a reply to message #633433]

Mon, 01 November 2010 17:58

Eclipse User

NB: You can only install Ascape Core Framework from http://ascape.sourceforge.net/eclipse (ie: org.ascape.core v5.6.0) if the AMP Escape (Incubation) feature has not been installed.

Re: Conflicting dependency when installing Ascape Documentation and Source [message #636566 is a reply to message #636565]

Mon, 01 November 2010 18:06

Eclipse User

Oliver Mannion wrote on Mon, 01 November 2010 17:58

NB: You can only install Ascape Core Framework from http://ascape.sourceforge.net/eclipse (ie: org.ascape.core v5.6.0) if the AMP Escape (Incubation) feature has not been installed.

Yep, that definitely makes sense. But are you able to install the other Ascape parts sans core? If not, it should be a simple matter of changing some dependencies so that that will work. I believe that has been done but I'm not sure the changes have been deployed to sourceforge.

Previous Topic:	Could not read class: ede.brook.model.CoordinationGame. Please ensure that the class exists in class
Next Topic:	Running models standalone

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Mar 20 22:04:06 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter