can tycho also quickly rewrite (change the manifest) of an jar that it wants to install?

[jcompagner]

Currently through the bnd tool tycho already generates correct manifest entries for a mvn jar that is not OSGi aware/configured.

What if a jar is that way? but it is not correctly done?
see my case here: apache/logging-log4j2#3787

the log4j-jakarta-web says it depends on jakarta [5.0,6.0) so that jar suddenly forces our bundles that depends just on log4j-core to use jakarta 5.0 but we are on 6.1 (build on top of tomcat 11)

because our bundle has an import jakarta.servlet version 6.1
log4j core where it also depends on has no jakarta.servlet stuff
but if we install also log4j-jakarta-web then log4j core is a Host of that fragment and then suddenly the classloader of that fragment is merged with the one of log4j core.. Then suddenly means that log4j core imports jakarta [5.0,6.0)
so installing that fragment suddenly forces us to use a lower jakarta.servlet..
But that log4j web jar shouldn't force that.. that runs fine on newer versions

So what i would like if i can just create a wrapped.xxxx one or something that i can adjust the import..

[laeubi]

What if a jar is that way? but it is not correctly done?

Like with every other software bug you should report it / help fixing and ask for a new release

So what i would like if i can just create a wrapped.xxxx one or something that i can adjust the import..

Download the jar and modify the manifest as you like or

https://tycho.eclipseprojects.io/doc/latest/tycho-wrap-plugin/wrap-mojo.html

[jcompagner]

i did report it but i have don't have big hopes that they will be fixed soon, for many of the apache projects OSGI is not really thought of and i think its now just auto generated so they are done with it..

of course i can download it and change it manually, and then place a version in our own maven repo... But that is not so nice (and have todo that with every release)