You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Karaman, Mehmet" <me...@advantest.com.INVALID> on 2025/03/14 13:45:29 UTC

bundle symbolic name in source jars MANIFEST.MF file.

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

Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Tom Mooney <to...@gmail.com>.
ta

On Fri, Mar 21, 2025 at 8:39 PM Gary Gregory <ga...@gmail.com> wrote:

> The best path to get a patch in is to submit a pull-request on GitHub.
> Don't forget unit tests that should fail if changes to the 'main' side of
> the source tree are not applied. The default Maven goal will run all build
> checks, make sure you run it locally and that is passws before you create a
> PR. See the PR template which explains all that.
>
> Gary
>
> On Fri, Mar 21, 2025, 16:29 Tom Mooney <to...@gmail.com> wrote:
>
> > Thanks for this. How do I get fixes in? Do I create a branch and
> > put that up for PR or put a fix up for a PR create a patch and attach it
> to
> > the tickets? etc
> >
> >
> > ta
> > Tom
> >
> > On Wed, Mar 19, 2025 at 6:52 PM Gary Gregory <ga...@gmail.com>
> > wrote:
> >
> > > Hello Tom,
> > >
> > > I would scan Jira and look for bugs to fix.
> > >
> > > It would be good to fix ASAP building on Java 23
> > > where FastDateParser_TimeZoneStrategyTest fails.
> > >
> > > HTHn
> > > Gary
> > >
> > >
> > > On Wed, Mar 19, 2025, 14:43 Tom Mooney <to...@gmail.com> wrote:
> > >
> > > > Hi All
> > > >
> > > > I'm new to the apache commons lang project. I'm an experienced
> software
> > > > developer 10+ years primarily with Java and would like to start
> > > > contributing to this project. Can someone give me advice/pointers to
> > how
> > > I
> > > > can get my first few contributions started and committed please?
> > > >
> > > > Ta
> > > > Tom
> > > >
> > > > On Fri, Mar 14, 2025 at 1:48 PM Karaman, Mehmet
> > > > <me...@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
> > > > >
> > > >
> > >
> >
>

Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Gary Gregory <ga...@gmail.com>.
The best path to get a patch in is to submit a pull-request on GitHub.
Don't forget unit tests that should fail if changes to the 'main' side of
the source tree are not applied. The default Maven goal will run all build
checks, make sure you run it locally and that is passws before you create a
PR. See the PR template which explains all that.

Gary

On Fri, Mar 21, 2025, 16:29 Tom Mooney <to...@gmail.com> wrote:

> Thanks for this. How do I get fixes in? Do I create a branch and
> put that up for PR or put a fix up for a PR create a patch and attach it to
> the tickets? etc
>
>
> ta
> Tom
>
> On Wed, Mar 19, 2025 at 6:52 PM Gary Gregory <ga...@gmail.com>
> wrote:
>
> > Hello Tom,
> >
> > I would scan Jira and look for bugs to fix.
> >
> > It would be good to fix ASAP building on Java 23
> > where FastDateParser_TimeZoneStrategyTest fails.
> >
> > HTHn
> > Gary
> >
> >
> > On Wed, Mar 19, 2025, 14:43 Tom Mooney <to...@gmail.com> wrote:
> >
> > > Hi All
> > >
> > > I'm new to the apache commons lang project. I'm an experienced software
> > > developer 10+ years primarily with Java and would like to start
> > > contributing to this project. Can someone give me advice/pointers to
> how
> > I
> > > can get my first few contributions started and committed please?
> > >
> > > Ta
> > > Tom
> > >
> > > On Fri, Mar 14, 2025 at 1:48 PM Karaman, Mehmet
> > > <me...@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
> > > >
> > >
> >
>

Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Tom Mooney <to...@gmail.com>.
Thanks for this. How do I get fixes in? Do I create a branch and
put that up for PR or put a fix up for a PR create a patch and attach it to
the tickets? etc


ta
Tom

On Wed, Mar 19, 2025 at 6:52 PM Gary Gregory <ga...@gmail.com> wrote:

> Hello Tom,
>
> I would scan Jira and look for bugs to fix.
>
> It would be good to fix ASAP building on Java 23
> where FastDateParser_TimeZoneStrategyTest fails.
>
> HTHn
> Gary
>
>
> On Wed, Mar 19, 2025, 14:43 Tom Mooney <to...@gmail.com> wrote:
>
> > Hi All
> >
> > I'm new to the apache commons lang project. I'm an experienced software
> > developer 10+ years primarily with Java and would like to start
> > contributing to this project. Can someone give me advice/pointers to how
> I
> > can get my first few contributions started and committed please?
> >
> > Ta
> > Tom
> >
> > On Fri, Mar 14, 2025 at 1:48 PM Karaman, Mehmet
> > <me...@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
> > >
> >
>

Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Gary Gregory <ga...@gmail.com>.
Hello Tom,

I would scan Jira and look for bugs to fix.

It would be good to fix ASAP building on Java 23
where FastDateParser_TimeZoneStrategyTest fails.

HTHn
Gary


On Wed, Mar 19, 2025, 14:43 Tom Mooney <to...@gmail.com> wrote:

> Hi All
>
> I'm new to the apache commons lang project. I'm an experienced software
> developer 10+ years primarily with Java and would like to start
> contributing to this project. Can someone give me advice/pointers to how I
> can get my first few contributions started and committed please?
>
> Ta
> Tom
>
> On Fri, Mar 14, 2025 at 1:48 PM Karaman, Mehmet
> <me...@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
> >
>

Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Tom Mooney <to...@gmail.com>.
Hi All

I'm new to the apache commons lang project. I'm an experienced software
developer 10+ years primarily with Java and would like to start
contributing to this project. Can someone give me advice/pointers to how I
can get my first few contributions started and committed please?

Ta
Tom

On Fri, Mar 14, 2025 at 1:48 PM Karaman, Mehmet
<me...@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
>

Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by "Karaman, Mehmet" <me...@advantest.com.INVALID>.
Hi Piotr,

maybe its only my usecase. We have a Test in our environment, which is checking the content of all Jar (also source jars) files and validates their MANIFEST.MF for various things regarding that.

The Apache commons bundles which are contained in the Eclipse-Orbit-repository (also their sources) are valid in our environment, but I was trying to use the recently build snapshot (which isn't conatined yet in the eclipse orbit repository) and put it in our environment. This failed because the MANIFEST.MF wasn't compatible with OSGI.

Thanks for your help, but it is too much overhead for "just being able" to see the source code temporarily. My problem will be solved automatically when the next Eclipse SimRel happens.

Best regards
Mehmet



________________________________
From: Piotr P. Karwasz <pi...@mailing.copernik.eu>
Sent: Tuesday, March 18, 2025 12:07 PM
To: dev@commons.apache.org <de...@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 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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by "Karaman, Mehmet" <me...@advantest.com.INVALID>.
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 <ga...@gmail.com>
Sent: Monday, March 17, 2025 1:20 PM
To: Commons Developers List <de...@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
<me...@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 <ga...@gmail.com>
> Sent: Saturday, March 15, 2025 2:47 PM
> To: Commons Developers List <de...@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
> <me...@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Gary Gregory <ga...@gmail.com>.
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
<me...@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 <ga...@gmail.com>
> Sent: Saturday, March 15, 2025 2:47 PM
> To: Commons Developers List <de...@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
> <me...@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by "Karaman, Mehmet" <me...@advantest.com.INVALID>.
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 <ga...@gmail.com>
Sent: Saturday, March 15, 2025 2:47 PM
To: Commons Developers List <de...@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
<me...@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: bundle symbolic name in source jars MANIFEST.MF file.

Posted by Gary Gregory <ga...@gmail.com>.
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
<me...@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org