[news.eclipse.platform] Re: Plugins with different versions, one as proj

["Manuel Steurer" <manuel.steurer@xxxxxxxxxxxxxxx>]

Thanks for your reply.

It's not really a solution to my problem,
since I want one project to depend on the old
version and not the new one. I have other projects
that do depend on the new version (under active
development), though.

It's no big deal and certainly no longtime situation
for me, it just struck me as odd.


Paul Webster wrote:

> Manuel Steurer wrote:
> > Hi,
> > 
> > I've got two versions of the same library-plugin, one as a jar-file
> > in the plugin-directory and the newer one as project in the
> > workspace. If I configure a dependency on another plugin to the old
> > version of my lib-plugin, Eclipse gives an error "Unsatisfied
> > version constraint". If I close the the lib-plugin-project, the
> > error goes away.  If I package both lib-plugin-versions as jars, it
> > also works.  Could this be a bug or am I doing something wrong?
> > 
> > I tested this on 3.3 and 3.4.
> > This is the line that gives the error:
> > 
> > Require-Bundle: de.qs.framework;bundle-version="[1.2.0,1.2.1)"
> > 
> > while having a plugin-project with version 1.2.1 and a jar with
> > version 1.2.0 in the plugin-dir.
> 
> AFAIK PDE picks your workspace project over your target platform
> plugin (that's standard).  Your version constraint precludes 1.2.1
> and PDE won't make 1.2.0 visible (hence the error).
> 
> I would say the solution (as you found) is to close your workspace
> project or change your version constraint to something like
> [1.2.0,1.2.1]
> 
> You can open an enhancement request against PDE as well.



--