Upstream software project

httpcomponents-project

Common POM file for HttpComponents

About httpcomponents-project

Common POM file for HttpComponents

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.httpcomponents-project: recorded package coverageopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
httpcomponents-project
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Common Maven POM file for HttpComponents. This project should be required only for building dependent packages with Maven. Please don't use it as runtime requirement.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package httpcomponents-project

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/Java): Common POM file for HttpComponents

    9-150400.1.6: noarch

    Source: httpcomponents-project

openSUSE Tumbleweed

  1. Package httpcomponents-project

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/Java): Common POM file for HttpComponents

    9-1.21: noarch

    Source: httpcomponents-project

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.