Closed rhierlmeier closed 2 years ago
The problem has been introduced with commit a7d600b1bf187a1e79ab30c6487dfa5b1d4f61ef. The change in line 252 is not correct.
I can reproduce the issue but changing line 252 of the commit does not solve the problem.
Interestingly the resolveVersionRange()
call finds the bundle
artifact version, but the subsequent resolveArtifact()
call does not find it. But removing the extension from the resolveArtifact()
call causes maven to not even find simple jar artifacts.
On the master branch I have added some small changes that map the bundle
packaging to jar
. I am not sure if this is correct, but in my case it resolved the issue. To be sure, I have asked a this question on stackoverflow.
I think you have to use MavenProject.getArtifact().getType() instead of MavenProject.getPackaging(). In addition you have to pass classier of to the constructor call.
The handling of the bundle artitacts was still not working. I made additional adjustments in PR #292. It is working with this fix on my projects.
Added two test bundles to PR #292.
Fixed: 0.15.5
Since the fix of issue #278 (since version 0.15.1) the japicmp-maven-plugin can no longer be used for OSGI bundles. I get the following exception:
The Maven project has packaging bundle: