[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] Internal API's or not
|
One way to find out if you have sufficient API is to not export any internal
package or export it as friend to listed egit bundles that need access. This
forces extenders to open enhancement requests with details on what API is
needed externally. As long as EGit team is reasonably responsive to these
requests, this process will lead to solid public API very quickly. When
internal packages are visible, it is too easy for extenders to just
reference internal code and not bother alerting the project to an API need.
The x-internal warning is not enough of an incentive.
Just my two cents.
- Konstantin
-----Original Message-----
From: egit-dev-bounces@xxxxxxxxxxx [mailto:egit-dev-bounces@xxxxxxxxxxx] On
Behalf Of Robin Rosenberg
Sent: Wednesday, April 03, 2013 12:53 PM
To: EGit developer discussion
Subject: [egit-dev] Internal API's or not
My claim is that the classes inside EGIt, with very few exceptions are for
internal use only, but then I really don't know how tied up we by users
today. Can we ban callers outside the EGit realm to some extent?
See https://git.eclipse.org/r/#/c/11328/
-- robin
_______________________________________________
egit-dev mailing list
egit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/egit-dev
