You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sis.apache.org by "Martin Desruisseaux (Jira)" <ji...@apache.org> on 2023/01/15 18:45:00 UTC
[jira] [Resolved] (SIS-86) Refactor @Configuration annotation into a real Configuration class
[ https://issues.apache.org/jira/browse/SIS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Desruisseaux resolved SIS-86.
------------------------------------
Resolution: Fixed
> Refactor @Configuration annotation into a real Configuration class
> ------------------------------------------------------------------
>
> Key: SIS-86
> URL: https://issues.apache.org/jira/browse/SIS-86
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Utilities
> Affects Versions: 0.3, 0.4, 0.5, 0.6, 0.7, 0.8
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Major
> Fix For: 1.4, 1.0
>
>
> The {{@Configuration}} annotation is currently for identifying various static method having a system-wide effect. We may consider regrouping all such methods in a central place, maybe in a new {{org.apache.sis.setup}} package. We could provide pre-defined configuration profiles, including:
> * {{STRICT}} - maximal level of strictness (duplicated values cause parsing errors, Bursa-Wolf parameters mandatory for datum shifts, _etc._).
> * {{DEFAULT}} - the default setting as a compromise between {{STRICT}} and {{LENIENT}}: duplicated values just produce warnings, but datum shifts still require Bursa-Wolf parameters.
> * {{LENIENT}} - still working even if the accuracy may be compromise (e.g. apply datum shifts even in the absence of Bursa-Wolf parameters).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)