How to best "mass update" MANIFEST-MF dependencies

[phermsdorf]

Hi,

I'm currently in the process of updating a pretty large mixed-mode maven reactor.

After updating the target file dependencies including some major version changes it is now neccessary to adjust a lot of Require-Bundle and/or Import-Package directives in a lot of MANIFEST.MF files.

Of course, managing dependency version by target platform and in the MANIFEST is to some degree redundant.
But currently these version ranges are in place and completly removing them might also not be the best.

Currently they lokk like this:

Require-Bundle: com.qualitype.config;bundle-version="[8.0.0,9.0.0)",
 com.qualitype.core;bundle-version="[8.0.0,9.0.0)",
 com.qualitype.core.rxp;bundle-version="[8.0.0,9.0.0)",
 com.qualitype.databinding.rxp;bundle-version="[8.0.0,9.0.0)",
...

and they should be changes to something like this:

Require-Bundle: com.qualitype.config;bundle-version="[11.0.0,12.0.0)",
 com.qualitype.core;bundle-version="[11.0.0,12.0.0)",
 com.qualitype.core.rxp;bundle-version="[11.0.0,12.0.0)",
 com.qualitype.databinding.rxp;bundle-version="[11.0.0,12.0.0)",
...

Since in the last tycho releases some cleanup/adjustment goals appeared i wondered if there is soemthing that can help to make these changes.

Compared to that the update of the same dependencies in the plain maven project is much more easier by using central managed version properties and/or dependencyManagement configuration.
Could one think of to have something similar for bundle dependencies or is that a complete wrong approach?

Any other idea to improve this tendious manual process is of cource more than welcome.

Thanks for any hints on this.
Bye Peter

[laeubi]

There is an update-manifest mojo but it was not much tested yet, maybe it works, maybe it would need some enhancements for your use-case.

If you want your manifest automatically manged you need to use automatic manifest type of projects:

• https://eclipse.dev/eclipse/news/4.28/pde.html#automatic-manifest
• https://www.youtube.com/watch?v=FZZA29JYewM

[phermsdorf]

Hi,

Thanks for the pointers.

I tried the update-manifest mojo but it fails with something like

Cannot resolve dependencies of project foundation:com.company.core.rxp:eclipse-plugin:11.0.0-SNAPSHOT
  with context {osgi.os=win32, osgi.ws=win32, org.eclipse.update.install.features=true, osgi.arch=x86_64, org.eclipse.update.install.sources=true}
   Software being installed: com.company.core.rxp 11.0.0.qualifier
   Missing requirement: com.company.core.rxp 11.0.0.qualifier requires 'osgi.bundle; com.company.core [11.0.0,12.0.0)' but it could not be found: See log for details

and the core bundle is one of these maven project that get's a manifest generated via maven-bundle-plugin. It actually exists and the core.rxp also defines a maven dependency to it. In the normal build it works.
Maybe that is a bug with mixed mode reactors.

Besides that it sounds from the decription that this mojo raises the lower bound, which is only part of the solution but nevertheless an intresting and useful feature.

The suggestion with the MANIFEST generation is very interesting function which I have seemed to miss till now.
I gave it a quick shot and tried to convert an existing bundle with the wizard.
My observations:

• I get a very long pde.bnd (like >100 lines) with a lot of buildpath entries - I removed them without any obvious change in the manifest generation
• I see this error for the converted plugin:
  
  maybe a configuration problem here ...
• the bounds of the imports (of course) are only as good as the exports on the other side. So for initial use-case/question it imports most of the packages without version, because they are exported without version ... so that only would work out when generating all bundle manifests in the end ...

I need to experiment with that a little further, since that would be a really big change but could out work really good ....

Thanks again @laeubi

Bye Peter