Hi Karaman,
On 18.03.2025 10:47, Karaman, Mehmet wrote:
Here is a short example of how the MANIFEST.MF has to look like: OSGi Modularity and
Services - Tutorial<https://www.vogella.com/tutorials/OSGi/article.html>. As I
see that the Eclipse Orbit is repackaging the apache commons bundles with an
appropriate MANIFEST.MF, so the best would be to wait until the next Eclipse SimRel
happens.
I've checked the other apache commons projects which are using the same parent
pom and also have a unappropriate source jar, so my confusion was how it comes
that there are OSGI compatible jars and why the SNAPSHOT builds are not OSGI
compatible 🙂. Now my question is solved.
All the Commons binary JARs are valid OSGi bundles.
I don't really understand, why do you need the `-sources` artifacts to
be OSGi bundles, since they don't contain any compiled classes? These
files are basically ZIP files with a `.jar` extension and they are only
useful to look up Java source code in an IDE. You can't even
build/reproduce the binary JAR with them, since they lack all the files
with build instructions.
Can you clarify, how you are using the `-sources` archives and why you
need any metadata to be present in the MANIFEST.MF file? As most OSGi
descriptors these days, the MANIFEST.MF file in Apache Commons is not
hand written, but generated using the `maven-bundle-plugin`. The plugin
only writes the manifest to the output directory `target/classes`, but
not to a directory that would end up in the `-sources` archive. Would
you expect the plugin to write the manifest to both?
See [1] for a similar question.
Piotr
[1] https://github.com/apache/logging-log4j2/issues/3255
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
