|Re: Conflicting dependency when installing Ascape Documentation and Source [message #632717 is a reply to message #632712]
||Thu, 14 October 2010 04:16
| Miles Parker
Registered: July 2009
|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?
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".
Powered by FUDForum
. Page generated in 0.01680 seconds