[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Need guidance/comments on package (re-)naming
|
Hi Martin,
I don't think the "ep" is the right segment for API, because
"extension point" is just a technology to contribute more
implementations. You may decide to support contribution via OSGi
components later - but the interface will be the same, right? So, I
think the extraction of "extension point API" is not a descriptive
point of view.
Regards,
AF
22.05.2020 20:06, 15 knots пишет:
Hi all,
my plugin has an API for consumers of the
plugin as well as an API for the extension point the plugin
provides.
The consumer API has 5 public classes and
interfaces in a single package whereas the extension point API
has 16 public classes and interfaces in 2 packages.
I want to keep these APIs separated.
Since the package of the consumer API currently
is a complete misnomer, I have to rename it.
So my question is: Are the any conventions in
CDT on naming the packages? Or could anybody help me to find
good package names?
The top level package (and name) of my plugin
is
org.eclipse.cdt.cmake.is.core.
Below that are
- the misnamed *.language.settings.providers
package which contains the consumer API and.
- the extension point API is in the top-level
package (not sure whether that is a good idea) and in the
sub-package *.builtins.
What do you think of having the consumer APi in
the top-level package (o.e.c.cmake.is.core) and having the 2
extension point API package to a package below
o.e.c.cmake.is.core? For example o.e.c.cmake.is.core.ep and
o.e.c.cmake.is.core.ep.builtins?
Please comment.
Martin
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
