|Re: Getting older versions from p2 [message #745474 is a reply to message #745128]
||Sat, 22 October 2011 21:14
| Miles Parker
Registered: July 2009
OK, I finally figured it out. I got the message above when I tried to specify a specific version from feature.xml. Here's what I'd tried..|
1. All plugin MANIFEST.MF that reference the bundle have the version range specified, that is: org.eclipse.emf.edit;bundle-version="[2.7.0,2.7.1)"
2. My feature.xml includes the containing features without any version qualifiers, e.g. <includes id="org.eclipse.emf.edit" version="0.0.0"/>
But *that* didn't work. It then grabbed both 2.7.0 and 2.7.1 and failed during the build with an unsatisifed depenendency, presumably because emf.edit is a singleton and it had already loaded 2.7.1. Why is not exactly clear. But I have a theory why it grabbed 2.7.1 in the first place... Even though the current version of emf.edit.ui is still 2.7.0, the build for emf.edit.ui was created for Indigo SR1, which assumes the emf.edit 2.7.1 version. When I:
3. Removed both the emf.edit.ui and emf.edit features and instead used the plugin dependencies.
Buckminster then grabbed the emf.edit 2.7.0 and not the 2.7.1. I'm not sure my theory is correct though, because it was the SR1 build version of emf.edit.ui that ended up in the build. The only other explanation is that Buckminster pulled the emf.edit 2.7.1 feature even though I had requested the 2.7.0 emf.edit plugin.
[Updated on: Sat, 22 October 2011 21:15]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02527 seconds