Re: [wildfly-dev] Updating WildFly instance with the Provisioning Tool

Currently the update feature pack inherit the provisioned feature packs so he would be able to reproduce the whole installation in a single step since the 'initial' installation would be applied then the customization. So basically a user makes some changes manually and we provide him with a feature pack. The produced feature pack is not just a feature pack with the changes but a 'real' feature pack installing everything (initial installation + changes). Of course he would have to either rebuild the feature pack or adjust it when he wants to use a new version of the installation feature packs (at least update the gav coordinates in the dependencies).  Detail question answer : Currently producing a feature pack is different from updating a provisioned instance : we could specify which files to ignore based on this (logs files don't mean anything if you want to install a customized instance multiple times but shouldn't be deleted if you apply an update). Emmanuel