[
http://jira.amdatu.org/jira/browse/AMDATU-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695#comment-12695
]
Bram de Kruijff commented on AMDATU-558:
----------------------------------------
Read the comments, not gonna argue ;)
1) If we stick with autoconf we should test the hell out of it. AFAIK it has
not been tested / processed since we decided to replace it with autoconf. There
was a code review and a patch by mh that I think was never applied
(AMDATU-506). Obvisouly it would also be nice to merge in the filter option and
get rid of the namescheme hack in there.
2) Though I will not argue over FELIX-3329 you must see that it does not cover
our use cases. The entire tenant mechanism is configuration based and thus
asynchronous and thus autoconf will fail (sometimes).
> Replace tenantconf deployment with Felix autoconf snapshot
> ----------------------------------------------------------
>
> Key: AMDATU-558
> URL: http://jira.amdatu.org/jira/browse/AMDATU-558
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu Core
> Reporter: Bram de Kruijff
> Assignee: Marcel Offermans
> Fix For: Sprint 5
>
>
> AMDATU-498 generalized the tenantconf enhancemente to standard Apache Felix
> autoconf/metatype. However, these changes have not yet been integrated into
> the platform build.
> TODO;
> * take snapshot of Felix autoconf/metatype
> * integrate in release / kitchensink
> * move tenantconf to attic
> * update documentation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
