Home » Eclipse Projects » Equinox » bundle-version matching
| bundle-version matching [message #65620] |
Fri, 28 April 2006 18:09  |
Eclipse User |
|
|
|
Originally posted by: joerg.von.frantzius.artnology.nospam.com
This is a multi-part message in MIME format.
--------------030209050008090907080604
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Hi,
when I tried to declare an exact version match using Eclipse 3.2. RC1a,
a bunch of problems came my way. For one, the manifest editor doesn't
store the maximum version
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=139224> (although one can
input it in the editor). But what seems to be the bigger problem is that
the resulting classpath for my plugin does not seem to match the
versions I specified.
In my configuration I have both EMF 2.2.0 and 2.1.1 present, and I
specified the following:
org.eclipse.emf.codegen;bundle-version="2.1.1";version-match=minor;visibility:=reexport,
org.eclipse.emf.codegen.ecore;bundle-version="2.1.1";version-match=minor;visibility:=reexport,
org.eclipse.emf.importer;bundle-version="2.1.1";version-match=minor;visibility:=reexport,
org.eclipse.emf.importer.java;bundle-version="2.1.1";version-match=minor;visibility:=reexport,
After chosing "Update Classpath" I end up with an interesting mixture of
versions both 2.2.0 and 2.1.1.
There had been some discussion of a new syntax for specifying version
matches < http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg00301.ht ml>
but I'm not sure whether that is supposed to work or not (the Manifest
editor doesn't like it at all, that's for sure).
Could someone of the Equinox experts comment on whether the above exact
version match is supposed to work or whether it is even tested to work
with the PDE's "Update classpath..." facility?
Thanks,
J
|
|
|
| Re: bundle-version matching [message #65813 is a reply to message #65620] |
Mon, 01 May 2006 19:51  |
 Thomas Watson
Messages: 503
Registered: July 2009 |
Senior Member |
|
|
You should use the version range syntax in the bundle-version attribute
org.eclipse.emf.codegen;bundle-version="[2.1.1,2.1.2)";visibility:=reexport,
org.eclipse.emf.codegen.ecore;bundle-version="[2.1.1,2.1.2) ";visibility:=reexport,
org.eclipse.emf.importer;bundle-version="[2.1.1,2.1.2)";visibility:=reexport,
org.eclipse.emf.importer.java;bundle-version="[2.1.1,2.1.2) ";visibility:=reexport,
The version range of "[2.1.1,2.1.2)" indicates anything from 2.1.1 up to
but not including 2.1.2. PDE UI does support the version range syntax
when specifying the properties of your required plug-ins or imported
packages.
|
|
|
| Re: bundle-version matching [message #65961 is a reply to message #65813] |
Tue, 02 May 2006 19:22 |
| Eclipse User |
|
|
|
Originally posted by: joerg.von.frantzius.artnology.nospam.com
Thanks Tom, that works!
Some of the EMF plugins of that particular release are versioned 2.1.0,
some 2.1.1, so I'm using the following now:
org.eclipse.emf.codegen;bundle-version="[2.1.0,2.1.1]";visibility:=reexport,
org.eclipse.emf.codegen.ecore;bundle-version="[2.1.0,2.1.1] ";visibility:=reexport,
org.eclipse.emf.importer;bundle-version="[2.1.0,2.1.1]";visibility:=reexport,
org.eclipse.emf.importer.java;bundle-version="[2.1.0,2.1.1] ";visibility:=reexport,
Regards,
Jörg
Tom Watson schrieb:
> You should use the version range syntax in the bundle-version attribute
>
> org.eclipse.emf.codegen;bundle-version="[2.1.1,2.1.2)";visibility:=reexport,
>
> org.eclipse.emf.codegen.ecore;bundle-version="[2.1.1,2.1.2) ";visibility:=reexport,
> org.eclipse.emf.importer;bundle-version="[2.1.1,2.1.2)";visibility:=reexport,
>
> org.eclipse.emf.importer.java;bundle-version="[2.1.1,2.1.2) ";visibility:=reexport,
>
>
> The version range of "[2.1.1,2.1.2)" indicates anything from 2.1.1 up
> to but not including 2.1.2. PDE UI does support the version range
> syntax when specifying the properties of your required plug-ins or
> imported packages.
|
|
|
| Re: bundle-version matching [message #66004 is a reply to message #65961] |
Tue, 02 May 2006 20:14 |
| Eclipse User |
|
|
|
Originally posted by: joerg.von.frantzius.artnology.nospam.com
This is a multi-part message in MIME format.
--------------090304010309060902060203
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
It seems that was a bit too early. After a few restarts, the PDE editor
now claims that the version constraints cannot be satisfied. Again I'm
seeing a funny versions mixtures in the "Plug-in Dependencies" classpath
containers. When I look at "Help / About Eclipse SDK / Plug-in Details",
I can see all required versions, though (next to the larger versions I
don't require).
I had exported my plugins while it worked (using a Windows box, for some
reason it complained about a version 0.0.0 of my plugin not found or
something on the Linux box), then installed them and now my two plugins
are happily running from within my Eclipse configuration.
Maybe there is a problem related to resolving versions within the
workspace, as it seems to work in the normal runtime environment.
Joerg von Frantzius schrieb:
> Thanks Tom, that works!
>
> Some of the EMF plugins of that particular release are versioned
> 2.1.0, some 2.1.1, so I'm using the following now:
>
> org.eclipse.emf.codegen;bundle-version="";visibility:=reexport,
>
> org.eclipse.emf.codegen.ecore;bundle-version="";visibility:=reexport,
>
> org.eclipse.emf.importer;bundle-version="";visibility:=reexport,
>
> org.eclipse.emf.importer.java;bundle-version="";visibility:=reexport,
>
>
> Regards,
> J
|
|
| |
| Re: bundle-version matching [message #66211 is a reply to message #66066] |
Thu, 04 May 2006 08:22 |
| Eclipse User |
|
|
|
Originally posted by: joerg.von.frantzius.artnology.nospam.com
It seems that the particular EMF plugins that I need cannot coexist in
different versions. To me it looks like only the largest version gets
loaded (while other EMF plugins can coexist in different versions). I
somewhat lost overview how that can happen, could it be due to an old
plugin.xml format, missing MANIFEST.MF or bad feature.xml or something
like that?
However, I can live with it (and we'll have to migrate to the latest
version sooner or later anyway...)
Thanks for answering,
Jörg
Tom Watson schrieb:
> I would suggest you open a bug against PDE->UI. In the bug report you
> should attach some testcase bundles that reproduce the problem. Also
> I assume you are trying on the latest Eclipse 3.2 builds?
|
|
|
| Re: bundle-version matching [message #66231 is a reply to message #66211] |
Thu, 04 May 2006 11:20 |
| Eclipse User |
|
|
|
Originally posted by: neil.integility.com
Joerg,
These plugins cannot coexist in different versions because they are
singleton bundles - ie you can only have one instance of the bundle
running, irrespective of versioning.
Unfortunately that is a requirement of any bundle that contributes to the
extension registry.
- Neil
|
|
|
| Re: bundle-version matching [message #66662 is a reply to message #66231] |
Fri, 12 May 2006 22:33 |
| Eclipse User |
|
|
|
Originally posted by: jfrantzius.nospamremove.web.de
Thanks for that information! Just for the records, this seems to be the
same issue as discussed in thread "The RSP bundle must be singleton?",
relating to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=137574
Neil Bartlett schrieb:
> Joerg,
>
> These plugins cannot coexist in different versions because they are
> singleton bundles - ie you can only have one instance of the bundle
> running, irrespective of versioning.
>
> Unfortunately that is a requirement of any bundle that contributes to
> the extension registry.
>
> - Neil
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 20:50:47 GMT 2024
Powered by FUDForum. Page generated in 0.04215 seconds |
] 
Search
Help
Register
Login
Home
