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

ta On Fri, Mar 21, 2025 at 8:39 PM Gary Gregory 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

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

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.

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

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 wrote: > Hello Tom, > > I would scan Jira and look for bugs to fix. > > It would be

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

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 wrote: > Hi All > > I'm new to the apache commons lang project. I'm an experienced softwar

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

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

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

.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 Re

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

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. As I see that the Eclipse Orbit is repackaging the apache commons bundles with

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

20 PM To: Commons Developers List 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,

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

> jar doesn't have for example the "Bundle-SymbolicName" field. > > Best regards > Mehmet > > > > From: Gary Gregory > Sent: Saturday, March 15, 2025 2:47 PM > To: Commons Developers List > Subject: Re: bundle sy

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

_ From: Gary Gregory Sent: Saturday, March 15, 2025 2:47 PM To: Commons Developers List 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

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

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-

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