Hi Gary, 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. Thank you. Best regards Mehmet OSGi Modularity and Services - Tutorial - vogella<https://www.vogella.com/tutorials/OSGi/article.html> OSGi uses the META-INF/MANIFEST.MF file (called the manifest file) from the standard Java specification to define its meta information. The Java specification defines that additional key/value pairs can be added to this file without affecting runtimes which do not understand these key/value combinations. www.vogella.com ________________________________ From: Gary Gregory <garydgreg...@gmail.com> Sent: Monday, March 17, 2025 1:20 PM To: Commons Developers List <dev@commons.apache.org> Subject: Re: bundle symbolic name in source jars MANIFEST.MF file. [EXTERNAL] This email is from outside, please confirm sender, title, content and whether you're expecting an email from this sender. If you have any doubt about the legitimacy of this email, please use the Report feature of Microsoft Outlook (instructions<https://myadvantest.sharepoint.com/sites/InformationSecurity/SitePages/en/report_email.aspx>). In case of a security incident click here<https://helpdesk.advantest.com/servicePortal/submitIncident?populateSR_id=334272>. Hi Mehmet, Does it even mean anything in OSGi to have a source JAR and a Javadoc JAR? I'm not sure it does. Do you have any links to OSGi documentation to help us understand this? A quick search did not reveal anything. What's the actual issue you are dealing with and trying to solve? You can always provide a PR on GitHub ;-) TY! Gary On Mon, Mar 17, 2025 at 4:30 AM Karaman, Mehmet <mehmet.kara...@advantest.com.invalid> wrote: > > Hi, > > thank you for the answer. The problem is that the source bundle isn't OSGI > compatible (the binary jar is OSGI compatible). The MANIFEST.MF of the source > jar doesn't have for example the "Bundle-SymbolicName" field. > > Best regards > Mehmet > > > ________________________________ > From: Gary Gregory <garydgreg...@gmail.com> > Sent: Saturday, March 15, 2025 2:47 PM > To: Commons Developers List <dev@commons.apache.org> > Subject: Re: bundle symbolic name in source jars MANIFEST.MF file. > > [EXTERNAL] This email is from outside, please confirm sender, title, content > and whether you're expecting an email from this sender. If you have any doubt > about the legitimacy of this email, please use the Report feature of > Microsoft Outlook > (instructions<https://myadvantest.sharepoint.com/sites/InformationSecurity/SitePages/en/report_email.aspx>). > In case of a security incident click > here<https://helpdesk.advantest.com/servicePortal/submitIncident?populateSR_id=334272>. > > > This is what I see in the source JAR's MANIFEST.MF > > Manifest-Version: 1.0 > Created-By: Maven Source Plugin 3.2.1 > Specification-Title: Apache Commons Compress > Specification-Version: 1.28 > Specification-Vendor: The Apache Software Foundation > Implementation-Title: Apache Commons Compress > Implementation-Version: 1.28.0-SNAPSHOT > Implementation-Vendor: The Apache Software Foundation > > The runtime JAR has what appears to be the normal runtime information. > > Can you be more specific? > > TY, > Gary > > On Fri, Mar 14, 2025 at 9:46 AM Karaman, Mehmet > <mehmet.kara...@advantest.com.invalid> wrote: > > > > Hello, > > > > Does it have a special meaning why the bundle symbolic name in the source > > jars MANIFEST.MF isn't contained? > > > > For example this one: > > Index of > > /repositories/snapshots/org/apache/commons/commons-compress/1.28.0-SNAPSHOT<https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-compress/1.28.0-SNAPSHOT/> > > > > The binary bundle has a correct MANIFEST.MF but the corresponding source > > has a different MANIFEST.MF (kind of chopped). > > > > Thank you in advance. > > > > Best regards > > Mehmet > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
