[
https://issues.apache.org/jira/browse/TAMAYA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400845#comment-15400845
]
Werner Keil commented on TAMAYA-169:
------------------------------------
It's not a bug if an API is either not modular enough or seems "too big". There
are plenty of real life use cases (connecting to Consul or other popular config
servers) that Tamaya (API+Core implementation) supports, so a bug would be some
of them broken or not working any more.
The GitHub mirror is more flexible to show branches, so I assume you plan to
help with this branch:
https://github.com/apache/incubator-tamaya/tree/tamaya-next
Tamaya is a result of the JCP EC not finding enough working use cases for
configuration to consider standardizing it when discussed by Anatole and
others. It's the PoC, not the JSR and except maybe in a future release acting
as Reference Implementation, JSR development will not happen here at Apache
Tamaya IMHO.
Ok, the only exception could become, if other JSRs like 362 (Portlet 3) were
forced to move their public API to an Apache repository, then an example case
for that would exist. Until then, https://github.com/java-config could be the
right place for an API.
> 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: Mark Struberg
>
> 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)
