[
http://jira.amdatu.org/jira/browse/AMDATU-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662#comment-12662
]
Bram de Kruijff commented on AMDATU-558:
----------------------------------------
The fileinstall will call the autoconf ArtifactHandler for each individual
create/touched/remove file. We can treat them as small deploymentpackages and
do a full DeploymentAdmin loop, but if we since we talk to the autoconf rp what
is the purpose?
Using DP namespace bundle locations would probably be nicely transparent to
deploymentadmin. Not sure if we can get in between though as FileInstall
handles bundles internally.
With regard to the loop I experience it may have to do with the fact that my
metatype files where not autoconf proof. I'd suggest first getting the
mechanism to work. If after that there is still a concern I'll create your
itest.
> 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
> 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
