[news.eclipse.platform] Re: No solution found because the problem in /tm

[John J Barton <johnjbarton@xxxxxxxxxxxxxxx>]

Andrew Niefer wrote:
> The problem is unsatisfiable means that p2 can't find a set of plugins 
> that satisfies all the requirements.  If you look at the errors one at a 
> time, it really isn't that hard.  (The hard part would be finding the 
> root cause).

Thanks Andrew. ...
> More non-overlapping version ranges, there are a bunch of these.  And 
> this is probably the root cause.  You are perhaps trying to install 
> something old into a 3.4.0 eclipse, and that old thing has dependencies on a 3.2.0 eclipse.

but what I was doing was installing something new -- a plugin I build 
with 3.4.1 eclipse update site thing -- in to 3.4.0 eclipse.

My gut feeling is that the dependency analysis is just wrong. I assume 
it relies on information I gave to eclipse when I built my plugin, stuff 
in the manifest.mf? other places? But I have no idea what all that stuff 
means and frankly I don't want to know. How can I build my plugin to 
work with a given eclipse version?  Somewhere I want to put "check 
against eclipse 3.4.0" and when users install I want the message to be 
either "success" or "you need eclipse 3.4.0". All that other stuff 
simply cannot be my users interface to my install.

Thanks,
John