Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework update system #66

Open
timvisee opened this issue Sep 3, 2017 · 0 comments
Open

Rework update system #66

timvisee opened this issue Sep 3, 2017 · 0 comments
Assignees

Comments

@timvisee
Copy link
Owner

timvisee commented Sep 3, 2017

Rework the whole updating system, and implement it properly.

Work with UpdateRequest and UpdateResponse objects, for creating general update requests and responses. The request object would hold whether updates should be automatically installed, and so on. The response object holds properties like whether an update is available, and whether it is installed.

Use a general updating system using adapters. The existing updaters should be modified to use these adapters. This would adding new updating systems easier later on.

The Bukkit updater should be wrapped to achieve as much as the wanted functionality as possible.

The update manager should provide a directory/file to an updater to download any file updates to. Installing downloaded update files should be generalized, as it doesn't make sense to reimplement this in each new updater.

Even though the updater that is used should be selected automatically, the option should be provided to switch to a different updater. It must be checked whether this is allowed when the plugin is released on Bukkit, as it might not be allowed to use a different updater than the one provided by Bukkit itself.

@timvisee timvisee self-assigned this Sep 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant