Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Feature Request: Make Jinjava Dependencies Easily Upgradeable

Offen
  • Stimmt etwas nicht?
#1,343 0 Kommentare 3 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
build-system

Rechercherichtung

The issue asks for a Java artifact that declares Jsoup and similar libraries as ordinary Maven dependencies instead of bundling them, so consumers can override versions in their own pom.xml. Start by finding where the build packages Jsoup into the Jinjava artifact, then decide how a distribution without it would be published. Done means a consumer can pin a patched Jsoup version through Maven with no Jinjava release, and the maintainers have agreed on the packaging approach.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Context

A security vulnerability has been identified in the version of Jsoup used by Jinjava. Since Jsoup is bundled directly into Jinjava, upgrading it through the consuming project's pom.xml is not straightforward.

This creates a dependency on a new Jinjava release to benefit from security fixes, potentially delaying remediation.

Proposed Improvement

Provide a Java distribution of Jinjava that exposes dependencies such as Jsoup as external Maven dependencies, with versions that can be overridden or upgraded independently through the consuming project's pom.xml.

Ideally, these dependencies should be declared as regular Maven dependencies rather than being shaded or embedded directly into the Jinjava artifact.

Benefits
  • Faster security remediation: Upgrade vulnerable dependencies without waiting for a new Jinjava release.
  • Improved dependency management: Let consuming projects control dependency versions through Maven.
  • Reduced security exposure: Minimize the time applications remain vulnerable to known security issues.
  • Greater flexibility: Make it easier to keep Jinjava-based applications aligned with dependency security policies.
Expected Outcome

A Jinjava Java artifact with externally managed, independently upgradeable dependencies, allowing consumers to apply security fixes as soon as patched dependency versions become available.

Vorherrschende Sprache
Java
Sterne
787
Forks
184
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus HubSpot/jinjava

Alle Issues in HubSpot/jinjava

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.