Open segevfiner opened 9 months ago
Any idea for a workaround?
m2e contains a testsuite so a first step should be to add a new testcase to demonstrate the issue and then add support for handling pom dependencies (what could get a bit tricky).
Beside that, its always good to ask people to add OSGi metadata in the first place.
That's more about fixing this. I'm looking for a way to add the dependency differently without hitting this issue. Expecting non-OSGi fans maintainers of libraries to add OSGi metadata to their jars is unlikely in my experience. OSGi is unfortunately kind of hostile towards the entirety of the existing ecosystem of Java libraries and even JPMS AFAIK...
Try the following target defintiion:
You will get the following error: