When Open Source Turns Sour: The JGit Licensing Clash That Split a Community

In 2023, a quiet but seismic shift in the open-source world sent shockwaves through the software industry when the JGit project, a critical Java-based implementation of Git used widely in enterprise and development tools, altered its licensing model under the Eclipse Foundation. Originally released under the permissive Eclipse Public License (EPL), which allowed broad commercial use without requiring full code disclosure, JGit introduced new ’commercial integration restrictions’—effectively adding clauses that targeted large corporations embedding the library deeply into proprietary products. While framed as a move toward sustainability and fair contribution from companies profiting from the technology, the change was perceived by many as a veiled attempt to monetize a foundational open-source component, undermining the trust that underpins collaborative development. This decision placed EGit, the Git client for the Eclipse IDE that relied entirely on JGit, in a precarious position. True to its open ethos, the EGit community responded by forking JGit to preserve the original EPL terms, ensuring continued unrestricted access for developers and organizations. The fork was not merely technical but symbolic—a stand against the creeping commercialization of shared infrastructure. The split highlighted a growing tension in open source: the struggle to fund essential projects without compromising the principles of openness and freedom. Large enterprises faced sudden compliance risks, forcing costly audits and potential rewrites of internal systems. Smaller developers and businesses worried about precedent, fearing that other widely used libraries might follow suit. The JGit/EGit episode revealed how licensing decisions—often invisible to end users—can disrupt supply chains, alter development roadmaps, and trigger community-led resistance. It underscored that open source is not just about code, but about governance, trust, and the balance of power between contributors, corporations, and communities. Today, both versions of JGit coexist: one evolving under revised terms with uncertain adoption, and the other maintained by the EGit community under the original, unencumbered license. This event serves as a pivotal case study in open-source sustainability, demonstrating both the fragility of consensus and the resilience of decentralized communities to self-correct when core principles are challenged. The long-term impact may be a more cautious approach to licensing changes in foundational software and a renewed emphasis on transparency and inclusivity in open-source stewardship.