Re: [jgit-dev] [VOTE] Making API incompatible changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jgit-dev] [VOTE] Making API incompatible changes

From: Alex Blewitt <alex.blewitt@xxxxxxxxx>
Date: Sat, 22 Jun 2013 00:23:23 +0100
Delivered-to: jgit-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jgit-dev>
List-help: <mailto:jgit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jgit-dev>, <mailto:jgit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jgit-dev>, <mailto:jgit-dev-request@eclipse.org?subject=unsubscribe>

On 22 Jun 2013, at 00:13, Shawn Pearce <spearce@xxxxxxxxxxx> wrote:

> OK so our next version should be 3.1?

I'd agree with that as well. 

It's conventional to mark anbstract classes with @noextend in a JavaDoc style comment to indicate that this class is not intended to be subclassed by users (and a similar @noimplement for interfaces). It would be useful to add that as well to help document the expectations that users aren't explicitly expected to subclass API classes. 

Alex

References:
- [jgit-dev] [VOTE] Making API incompatible changes
  - From: Shawn Pearce
- Re: [jgit-dev] [VOTE] Making API incompatible changes
  - From: Gunnar Wagenknecht
- Re: [jgit-dev] [VOTE] Making API incompatible changes
  - From: Matthias Sohn
- Re: [jgit-dev] [VOTE] Making API incompatible changes
  - From: Shawn Pearce

Prev by Date: Re: [jgit-dev] [VOTE] Making API incompatible changes
Next by Date: Re: [jgit-dev] [VOTE] Making API incompatible changes
Previous by thread: Re: [jgit-dev] [VOTE] Making API incompatible changes
Next by thread: Re: [jgit-dev] [VOTE] Making API incompatible changes
Index(es):
- Date
- Thread

Breadcrumbs