Delete old files automatically about update4j

[mordechaim]

It's a bit a risky operation, and unless you use the same filename it's somewhat out of the scope of this framework.

Of course, nothing keeps you from doing this logic yourself in a custom bootstrap application.

[AG72]

Thanks for your quick answer (and thanks for update4j!) , so for now I will just reuse the same filename and be happy.

[mordechaim]

Just noticed your file name indicate that you are asking about bootstrap modules, i.e. an update handler.

Files like this cannot really be deleted/overwritten, since it loads unto the JVM when the framework launches (on Windows they are locked, on UNIX it is just unsafe to overwrite, although it's not locked).

Here is where the versioning come in; just leave them there (you can remove them from config though), release a new version with new filename and increment the version() and let update4j do the rest.

[AG72]

The filename I chose in the example was a bit misleading. In fact I have an application using lots of external dependencies as e.g. Spring framework. In case a new version of that framework is released and I update the update4j configuration to the new version, I will have both versions in my "boot" directory on the client that is synced by update4j.

It is not a real problem since the old libraries are not on the classpath when update4j launches the client after syncing the files, the idea was to keep the "boot" directory clean and not growing too much over the time.
This could be achieved by a delta mechanism that compares the files in the clients configuration before and after syncing and then - of course secured by an extra option in the configuration - deletes obsolete files.

[mordechaim]

After much thought I came up with a design that uses your idea and still nicely fits into the rest of the framework.

I'm going to implement/test it soon.

[AG72]

I'm looking forward for this feature. Thank you!

[mordechaim]

Need testers for Linux.