[windup-dev] Automatic upgrading (of the whole app) discussion

[Ondrej Zizka]

Regarding cache/, as the name hints, it can get recreated, and I'd opt 
for that, even if it would take some time - it's more robust approach.
Other dirs, I think what's left is the ignore stuff, I'd convert as 
well. But since it's user editable stuff, it might need some merging.

Ondra



On 30.7.2015 10:47, Marek Novotny wrote:
> well we both probably meant the same way as you said the replacing files
> on the fly is problematic.
>
> I would say I am fine with that.
> Btw are directory like  cache significant too in addition to ignore and
> rules directories in end user customization?
>
> On 29.7.2015 10:20, Ondrej Zizka wrote:
>> Ah, here I found this post.
>>
>> I am not sure about cloning. Only the rules could be potentially needed
>> to transfer. And maybe the .ignore files.
>> Hence I'd rather swap the whole distro directories and then transfer the
>> XML rules. To keep the process simple and to avoid collisions when we
>> change some dir structure.
>>
>> WDYT?
>> Ondra
>>
>>
>> On 28.7.2015 10:27, Marek Novotny wrote:
>>> First of all I think this gather to windup-dev list.
>>>
>>> Secondly I think the safest way is to clone the current distribution and
>>> do the upgrade on it and then before shutdown the furnace just copy
>>> cloned and upgraded distro back to current place.
>>>
>>>
>>>
>>> On 28.7.2015 03:43, Ondrej Zizka wrote:
>>>> Hi all,
>>>>
>>>> what should be the approach to upgrading?
>>>>
>>>> Current implementation simply replaces the files on the fly (as a
>>>> command), and it seems it isn't bulletproof. Changing files under
>>>> Furnace's hands seems to break things. I get various FileNotFound and
>>>> dependency failures. Also, we currently do not have a way to run other
>>>> command than windup-migrate-app.
>>>>
>>>> Other approach could be to download the file, unzip to a temp directory,
>>>> and right before Windup's process shuts down, after Furnace is closed,
>>>> it would swap the existing and the new directories.
>>>> So next time, the new version would boot.
>>>> Would that be ok?
>>>>
>>>> Then we would need to address the possibility of rules changed by the
>>>> user inside of the windup directory.
>>>>
>>>> Ideas?
>>>> Ondra
>>>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>