Resolute Plugin Installation Issue – Version Constraints in MANIFEST Files

35 views
Skip to first unread message

Yara Hallak

unread,
Jul 11, 2025, 1:36:10 PMJul 11
to OSATE

Hello,

While installing Resolute as a set of plugins in OSATE, I encountered multiple errors due to strict upper version limits in the Require-Bundle declarations of the MANIFEST.MF files.

In particular, some bundles had version constraints like:

org.osate.aadl2;bundle-version="[2.0.0,6.0.0)", org.osate.aadl2.modelsupport;bundle-version="[2.0.0,8.0.0)", org.osate.xtext.aadl2.errormodel;bundle-version="[2.0.0,8.0.0)",

Since newer versions of these dependencies were available in my OSATE installation, the version constraints caused the plugins to fail to resolve.


To resolve the issue, I manually edited each MANIFEST.MF file under META-INF in the plugin projects and removed the upper version bounds (i.e., changed the version range to something like [2.0.0,) or left it unspecified).

This allowed the plugins to load properly with the newer versions of OSATE dependencies.


I recommend avoiding strict upper bounds in future versions unless absolutely necessary, as they can cause compatibility issues when newer, still-compatible versions of OSATE are released.

Hope this helps anyone facing the same issue!

Rakshit Mittal

unread,
Jul 13, 2025, 6:40:42 AMJul 13
to OSATE
Thanks!
I think its best if you open an issue here https://github.com/loonwerks/Resolute/issues
Or a pull request with your changes on the same repo.

Reply all
Reply to author
Forward
0 new messages