You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Naming_Conventions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ The names of API packages need to make sense to the ISV.
104
104
The number of different packages that the ISV needs to remember should be small, since a profusion of API packages can make it difficult for ISVs to know which packages they need to import.
105
105
Within an API package, all public classes and interfaces are considered API.
106
106
The names of API packages should not contain internal, tests, or examples to avoid confusion with the scheme for naming non-API packages.
107
-
Consult [Eclipse/API Central](/Eclipse/API_Central"Eclipse/API Central") for more detailed information on choosing and naming API elements.
107
+
Consult [Eclipse/API Central](https://github.com/eclipse-platform/eclipse.platform/blob/master/docs/Provisional_API_Guidelines.md) for more detailed information on choosing and naming API elements.
0 commit comments