Spork: Structured Merge for Java with Formatting Preservation
Not on the map. Why?
Abstract (arXiv)
The highly parallel workflows of modern software development have made merging of source code a common activity for developers. The state of the practice is based on line-based merge, which is ubiquitously used with "git merge". Line-based merge is however a generalized technique for any text that cannot leverage the structured nature of source code, making merge conflicts a common occurrence. As a remedy, research has proposed structured merge tools, which typically operate on abstract syntax trees instead of raw text. Structured merging greatly reduces the prevalence of merge conflicts but suffers from important limitations, the main ones being a tendency to alter the formatting of the merged code and being prone to excessive running times. In this paper, we present SPORK, a novel structured merge tool for JAVA. SPORK is unique as it preserves formatting to a significantly greater degree than comparable state-of-the-art tools. SPORK is also overall faster than the state of the art, in particular significantly reducing worst-case running times in practice. We demonstrate these properties by replaying 1740 real-world file merges collected from 119 open-source projects, and further demonstrate several key differences between SPORK and the state of the art with in-depth case studies.
Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). First posted on arXiv 10 Feb 2022.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2026: 2.
2 papers.
- 2026Rover: Context-aware Conflict Resolution with LLMcited by 1
- 2026Merge-Bench: Resolve Merge Conflicts with Large Language Modelscited by 0
- 2026Merge-Bench: Resolve Merge Conflicts with Large Language Models25 May 2026
- 2026Rover: Context-aware Conflict Resolution with LLM17 May 2026