Skip to content

Migration to GitHub & Roadmap to v0.6.0 #1

Open
6 of 6 issues completed
Open

Description

@szkiba

ini4j is officially migrating from SourceForge (Subversion) to GitHub to modernize the development workflow and facilitate community contributions.

The full history of the project (dating back to 2005) has been preserved.

📅 Roadmap to v0.6.0

The goal of the 0.6.0 release is to modernize the internal structure, fix critical security issues, and launch a modern documentation site.

Phase 1: Infrastructure

  • Migration: Migrated SVN trunk, branches, and tags to Git.
  • Distribution: Verified Sonatype OSSRH access for org.ini4j.
  • Repository Config: Make repository Public.
  • Dev Environment: Configure .devcontainer for VS Code/Codespaces.
  • Domain: Register ini4j.dev (DNS setup pending Phase 3).

Phase 2: Code Modernization

  • Modernize POM:
    • Update compiler source/target to Java 17.
    • Remove legacy SVN metadata and wagon plugins.
    • Update Maven plugins to latest stable versions.
  • Code Quality: Reformat Java code, set up VS Code extension for automatic formatting, and add Maven plugin for automatic verification.
  • CI/CD: Set up GitHub Actions (Java 17 CI) once the build is stable.
  • Security Fix (Critical): Patch CVE-2022-41404 (DoS vulnerability in BasicProfile variable expansion).
  • Add Javadoc documentation to public API
  • Project Identity: Update README.md and create CONTRIBUTING.md.
  • Prepare for Modules: Add Automatic-Module-Name: org.ini4j to JAR manifest.

Phase 3: Documentation & Release

  • New Website: Refactor legacy documentation into a modern Astro Starlight site.
  • Deploy: Connect GitHub repo to Vercel for automatic deployments to ini4j.dev.
  • Publish: Release v0.6.0 to Maven Central.

Phase 4: SourceForge Sunset

  • Status Update: Update SourceForge metadata to "Moved".
  • Lockdown: Disable Code, Tickets, and Discussion tabs on SourceForge.
  • Redirects: Replace legacy htdocs with .htaccess 301 redirects to ini4j.dev.

If any issues with the migration are found, please comment below.

Activity

  1. self-assigned this
    on Jan 27, 2026
  2. tswern commented on Nov 10, 2026

    @tswern

    Thanks for migrating ini4j to GitHub and for merging the CVE-2022-41404 fix (#10), good to see the project active again.

    A request from a downstream consumer: would you consider publishing an interim, security-only release (e.g. 0.5.5) containing just dda3743, ahead of the full v0.6.0 scope?

    0.5.4 (2015) is still the only artifact on Maven Central, and OSV / Trivy / GitHub Advisory all flag it for CVE-2022-41404 (CVSS 7.5). Because the fix is merged but unreleased, downstreams currently have to vendor a locally-patched jar to pass security scanners. An interim 0.5.5 with only the security fix would let everyone drop those patches right away, while v0.6.0’s documentation work (Phase 3) continues on its own timeline. OSSRH access for org.ini4j is already verified per this issue, so it should be low-effort.

    Happy to help test a release candidate. Thanks again for picking this up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions