Re: [jgit-dev] Proposed API breakage forcing us to JGit 2.0

[Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>]

2012/2/13 Shawn Pearce <spearce@xxxxxxxxxxx>

https://git.eclipse.org/r/5079 proposes an API change that will force
the project to bump our major revision number.

I can't really think of a sane way to avoid this. Given how few
customers probably embed ReceivePack, or implement the interface in
question, forcing customers to update their code may be cleaner than
trying to maintain compatibility inside of JGit.

there are a few more breaking changes in the queue mainly around cleaning

up exception handling, see [1]. Please add all such cases to this bug so

that we have an overview what's cooking here. 

On Hudson we generate a compatibility report comparing the current build 

against the last published release [2]. As soon as [3] is fixed we can also 

generate this report on every change pushed for code review.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=369461

[2] https://hudson.eclipse.org/hudson/job/jgit/ws/org.eclipse.jgit/target/site/clirr-report.html

[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=370010

-- 
Matthias