-
-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when a dependency is a POM-packaging module #5349
Comments
There is something odd here. We already have code which confirms the file is a valid zip. bnd/maven/bnd-maven-plugin/src/main/java/aQute/bnd/maven/plugin/AbstractBndMavenPlugin.java Lines 305 to 318 in 0f84dc5
Can you please provide a small github repo which demonstrates the problem? Then we can investigate. Thanks. |
bjhargrave
added a commit
to bjhargrave/bnd
that referenced
this issue
Aug 19, 2022
Since we care about the file and not just the artifact object, we check the file name for ending in ".jar" (jar extension) instead of relying on the artifact reporting the "jar" type. Fixes bndtools#5349 Signed-off-by: BJ Hargrave <[email protected]>
I made a small change in #5351 which may address this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am experiencing an issue when building in Eclipse / m2e that apparently a "pom" file ends up on the classpath and this breaks the bnd-maven-plugin.
The "pom" belongs to a module with "pom" packaging that is included transitively through a test dependency.The "pom.xml" belongs to a module with packaging "jar" - but it does not really include any code. Changing the packaging of that module to "pom" seems to resolve the issue.As far as I can see, the code that collects the buildpath in
AbstractBndMavenPlugin
goes through all the runtime artifacts and adds them to the buildpath. This code also seems to check if an artifact is actually a JAR/ZIP ... no idea how the "pom.xml" slips through...Stack trace:
bnd: 6.3.1
The text was updated successfully, but these errors were encountered: