| [news.eclipse.platform] Re: No solution found because the problem in /tmp/p2Encoding13004.opb is unsatisfiable. |
First of all, it is not an option for you to be ignorant about dependencies and installation management if you're going to be a plugin publisher. It is just as important as understanding how to use SWT or what to do in your Activator start/stop methods, etc; it goes with the territory.
Now, if you want to target a particular version of particular plugins (remember, each plugin can be updated and change its version independently), you need to specify that in your plugins' Dependency
list. For each plugin listed as a Dependency, you can (and should) specify a version range that is acceptable. Of course it is not a trivial matter, you have to think about the version ranges you want to allow: too restrictive and your stuff won't be compatible with arbitrary Eclipse instances; too loose and you'll get installed into environments that aren't really compatible with your code.
This is all part of designing a plugin or plugins - you have to think about what your target environment requirements are and embed that info into your plugin(s) dependencies and possibly your Feature definition.
I know the requirements, I don't know how to tell eclipse to use them.
jjb