sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SIS-185) Define the commited API for Shapefile
Date Mon, 22 Dec 2014 05:17:13 GMT

     [ https://issues.apache.org/jira/browse/SIS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Desruisseaux updated SIS-185:
------------------------------------
    Description: 
We should define the first elements of what would be the committed API for {{Shapefile}}.
The intend of this task is not to define the full API neither to change implementation details
that are not visible through the API. The intend is only to reduce the size of the public
API to elements that, we think, have good chances to stay there.

This task is targeted for completion before SIS 0.5 release. The intend is to give some guarantees
to Apache SIS 0.5 users that their code is likely to compile and run with Apache SIS 0.6.
To achieve this goal, the proposal is to hide the API elements which are likely to change,
for preventing users to depend on it. Those API elements can be hidden either by declaring
them package-privated, or by moving them in any {{org.apache.sis.internal}} sub-package, depending
on which approach is the less disruptive for the code.

  was:
We should define the first elements of what would be the committed API for {{Shapefile}}.
The intend of this task is not to define the full API neither to change implementation details
that are not visible through the API. The intend is only to reduce the size of the public
API to elements that, we think, have good chances to stay there.

This task is targeted for completion before SIS 0.5 release. The intend is to give some guarantees
to Apache SIS 0.5 users that their code is likely to compile and run with Apache SIS 0.6.
To achieve this goal, the proposal is hide the API elements which are likely to change, for
preventing users to depend on it. Those API elements can be hidden either by declaring them
package-privated, or by moving them in any {{org.apache.sis.internal}} sub-package, depending
on which approach is the less disruptive for the code.


> Define the commited API for Shapefile
> -------------------------------------
>
>                 Key: SIS-185
>                 URL: https://issues.apache.org/jira/browse/SIS-185
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Shapefile
>            Reporter: Martin Desruisseaux
>
> We should define the first elements of what would be the committed API for {{Shapefile}}.
The intend of this task is not to define the full API neither to change implementation details
that are not visible through the API. The intend is only to reduce the size of the public
API to elements that, we think, have good chances to stay there.
> This task is targeted for completion before SIS 0.5 release. The intend is to give some
guarantees to Apache SIS 0.5 users that their code is likely to compile and run with Apache
SIS 0.6. To achieve this goal, the proposal is to hide the API elements which are likely to
change, for preventing users to depend on it. Those API elements can be hidden either by declaring
them package-privated, or by moving them in any {{org.apache.sis.internal}} sub-package, depending
on which approach is the less disruptive for the code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message