[jira] [Resolved] (TAMAYA-169) streamline the API and work towards a JSR proposal

["Anatole Tresch (JIRA)" <ji...@apache.org>]

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

Anatole Tresch resolved TAMAYA-169.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Anatole Tresch  (was: Mark Struberg)

Decision was made NOT to change the API, since
* it is already used by a couple of users/companies
* it starts getting broader adoption

Just remember: it was not the conceptual part that was missing to start a JSR, but the adoption, where enough common sense must be so s standardization may be useful.
Due to this I close this ticket. We will continue our work with the given API (which is still small compared to other JSRs). I am confident that we can raise adoption. If a JSR starts soimehow, we will engage I think as well. Nevertheless our API is proven on real world use cases, all the other team members have and also was discussed at several hacker gardens, JUG events etc. 

> streamline the API and work towards a JSR proposal
> --------------------------------------------------
>
>                 Key: TAMAYA-169
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-169
>             Project: Tamaya
>          Issue Type: Improvement
>          Components: API
>            Reporter: Mark Struberg
>            Assignee: Anatole Tresch
>
> The current Tamaya API is a tad too large to be easily understandable. It contains many nice features, but many of them are not core-features.
> I'd like to provide a very minimal set of absolutely necessary classes and interfaces.
> For a prototype see
> https://github.com/struberg/incubator-tamaya/tree/jsr-proposal/jsr/api/src/main/java/tamaya/config



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