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

[John J Barton <johnjbarton@xxxxxxxxxxxxxxx>]

John J Barton wrote:
> Eric Rizzo wrote:
> > On 12/11/2008 2:54 PM, John J Barton wrote:
> ...
> > > Or is the simple answer that I have to build my plugin with exactly the
> > > version of eclipse that I want users to install?
> >
> > Well, for one thing you should ALWAYS be using a target platform, not 
> > building against the Eclipse that you are running as your IDE. It 
> > really irritates me that the default setup for the PDE is to use the 
> > running Eclipse as the target platform, because it can easily lead 
> > newbie plugin developers down a path with pitfalls. I suspect that is 
> > what has happened to you.
> > Here is one article explaining why: 
> > http://rcpquickstart.com/2008/04/21/why-create-a-custom-target-platform/
> > Here's the relevant Help page: 
> > http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm 
>
>
> Thanks. I can see that it helps a lot if I want to use my 3.4 eclipse to 
> build a plugin for 3.3. But as we know, I should be able to build a 
> plugin with 3.4.1 that runs on 3.4.0.  If I can figure out how to get it 
> to install.
>
> Does the target platform setting alter the MANIFEST.MF values?

Well the target platform settings certainly alters the build path and UI 
that builds the content for MANIFEST.MF.

After setting the target platform I got 5320 errors (!). That's because 
I have no plugins on my build path now. In the plugin.xml/MANIFEST.MF 
tool Dependencies page my Required Plugins Add button now only lists 
plugins in my project, none from eclipse.

Ah, got it: the target platform selector has to point to the 'plugins' 
directory. If you point it to "eclipse" it loads some plugins but not 
all of them.

So I built against a target platform on win32 and tried to install 
against the same version on Linux: install fails.

John.