Instructions in target won't be executed in certain cases #53
Replies: 1 comment
-
Please use discussions to ask questions, and keep in mind that the functionality in question is provided by m2e and reused by Tycho, so technically those are more appropriate places to ask. The problem is that you cannot re-wrap something that is already an OSGi artifact in Maven Central. E.g., any bundle in this table cannot be changed via BND instructions, which are simply ignored in that case. https://download.eclipse.org/tools/orbit/simrel/maven-osgi/table.html You'd need to literally strip out the MANIFEST.MF from the jar and then it could be processed. You're probably bother by the change in the bundle symbolic name, but you'd best accommodate that in the long term. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am working on a simpler repository in which I need some bundle snapshots (and two release version bundles). I've added instructions to create a bundle manifest, which isn't concerned by the target platform. The locations are maven locations and the resulting bundle symcbolic name is always ${mvnGroupId}.${mvnArtifactId} .. But in the instructions I've used hardcoded "org.apache.commons.compress".
Is there any place where I can check the error or something which tells me whats wrong with it? I've attached my target file (as txt file to be able to upload, so just remove the .txt from the extension).
Thank you in advance.
Best regards
Mehmet
MavenBND2.target.txt
Beta Was this translation helpful? Give feedback.
All reactions