Package: jaxb-api (4.0.0-bp160.1.11)

Jakarta XML Binding API

Das Jakarta XML Binding stellt eine API und Werkzeuge bereit, die die Abbildung zwischen XML-Dokumenten und Java-Objekten automatisieren.

Package information

Homepage
[https://github.com/eclipse-ee4j/jaxb-api]
License
BSD-3-Clause
Downstream-Paketbetreuer
Unbekannt: in der indizierten Quelle nicht gemeldet
Quellpaket
[jaxb-api]
Software project
[jaxb-api]

Versions and downloads for jaxb-api

Version / releaseArchitecture / repositoryPackage sizeInstalled sizeFilesPublisher repository artifact
4.0.0-bp160.1.11leap-16.0 / ossnoarchopenSUSE Leap 16.0 · OSS · multi-architecture113 KiB127 KiBlist of filesjaxb-api-4.0.0-bp160.1.11.noarch.rpm
4.0.0-160000.1.1leap-16.0 / ossnoarchopenSUSE Leap 16.0 · OSS · multi-architecture113 KiB127 KiBlist of filesjaxb-api-4.0.0-160000.1.1.noarch.rpm
About these downloads

Jede Zeile ist Paketindex-Metadaten für eine Version, Architektur, Suite und ein Repository. Namen, URLs und Größen stammen aus der Quelle; ein Link ist ein veränderbarer Abrufort, kein Weitergabanspruch von OpenFactory.

Other packages built from jaxb-api

Dependencies and recommendations for jaxb-api

  • dep: java-headless (>= 1.8)

    Package not available

  • dep: [javapackages-filesystem]

    Dateisystemlayout für Java-Pakete

  • dep: mvn(jakarta.activation:jakarta.activation-api)

    Package not available

Paketdateipfade (10)

Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.

  • /usr/share/doc/packages/jaxb-api
  • /usr/share/doc/packages/jaxb-api/README.md
  • /usr/share/java/jaxb-api
  • /usr/share/java/jaxb-api/jakarta.xml.bind-api.jar
  • /usr/share/licenses/jaxb-api
  • /usr/share/licenses/jaxb-api/LICENSE.md
  • /usr/share/licenses/jaxb-api/NOTICE.md
  • /usr/share/maven-metadata/jaxb-api.xml
  • /usr/share/maven-poms/jaxb-api
  • /usr/share/maven-poms/jaxb-api/jakarta.xml.bind-api.pom

Field source: openSUSE Leap 16.0 OSS

Bekannte Sicherheitslücken

Keine passenden Meldungen in den erfassten Quellen.

Zuletzt synchronisiert:

[CVE-Katalog]

Prüfsummen

Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.

4.0.0-bp160.1.11 / noarchBeobachtet Sep 1, 2026sha512 a8deff8395a9…a9a617cbPrüfsumme der Quelle

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Prüfsumme der Quelle (sha512): a8deff8395a972e7b5d3ea3899311f195010c35d55e2015914cfce4c43eab49be04488bd2b7745159ad4c33bc2585652b981495fcba01db123e7a14aa9a617cb

Field source: openSUSE Leap 16.0 OSS

4.0.0-160000.1.1 / noarchBeobachtet Sep 1, 2026sha512 7968202c5cb2…14969d82Prüfsumme der Quelle

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Prüfsumme der Quelle (sha512): 7968202c5cb265a5f40f63f3b27d18143723042a8667c4aca151048c8fc7902fc6d23d7e8436563db17c6428f3f52f5246418681495a488d2695e43314969d82

Field source: openSUSE Leap 16.0 OSS

Quellen

  • Authoritative source; repository metadata signature verified

    Signaturnachweis

    leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

    Repository-signature verification record
    Signed-object SHA-256
    271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable

Dieses Paket verwenden

OpenFactory kann dieses Betriebssystem in einer Browser-VM starten oder einen Image-Build mit dem nativen Paketnamen aus diesem Datensatz beginnen.