[
http://jira.amdatu.org/jira/browse/AMDATU-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATU-277.
-------------------------------------------
Assignee: Bram de Kruijff
Resolution: Fixed
Added fileinstall to the release project and disabled config-filebased (without
actually removing it). Config files are still physically located in
src/main/resources/conf of the config-filebased, but deployed to /deploy by the
release project. Fileinstall works two-way with Felix web console; config
updates in felix web console are also written to config files in the /deploy
directory.
Bram, please test and review
> Re-introduce fileinstall to autodeploy config files and bundles
> ---------------------------------------------------------------
>
> Key: AMDATU-277
> URL: http://jira.amdatu.org/jira/browse/AMDATU-277
> Project: Amdatu
> Issue Type: Improvement
> Components: Amdatu Core
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Bram de Kruijff
> Fix For: 0.1.0
>
>
> As of 0.0.5 config has been refactored from fileinstall and fileinstall was
> removed completely in 0.1.0-SNAPSHOT. However, we must support this use case
> in 0.1.0:
> - Download Amdatu distribution
> - Unzip, append custom bundles, zip
> - Send zip to the admin, he will
> o Unzip
> o Change configuration (like hostname and port of the http service) prior
> to first boot
> o Start Amdatu
> Reintroducing fileinstall is a very simple way to resolve this, until
> provisioning can take over this functionality.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
